ZOS,
there are multiple threads on this forum, as well as the foreign language forums, regarding the "unknown error". As I am on the receiving end of this I have done extensive research. In response to all these threads you have launched the thread
http://forums.elderscrollsonline.com/discussion/65328/unknown-error-received-upon-disconnecting/ in order to collect problem times and IP addresses of those affected. This thread was launched on 02.04 but until today there has been no update to from you with regards to a possible fix or a suggestion from support how to deal with this issue.
Also, because to this error message has no actual error code attached to it, it is unlikely that all people receiving the "unknown error" have the exact same problem.
I have seen multiple fixes on these forums, some of them worked for a minority, for most however nothing has changed:
- Running ESO and the launcher as administrator within Windows
- Opening up the ports 24100 through 24500 as well as 24131 through 24507 for both TCP and UDP
- Closing the launcher in the background when running ESO
- Adding ESO to the allowed programs in the firewall
- Disabling addons
My specific problem is that: Whenever I log into ESO, I get to the character selection screen and into the actual game without any problem. However when in game I cannot: Use an ability, interact with NPCs and objects, draw weapons. In addition I see other players move erratically through the area as if there is some massive lag. Whenever I try to do one of these functions such as using an ability or interact with an object I get the unknown error after about 20 seconds. When logging into the game multiple times, there is the rare occasion that all is working perfectly fine. This is up until I am moving from one zone to the next (eg. Dungeon -> Quest area or Dungeon -> Waypoint) and then the whole thing starts again.
I would like to hear from other players if they are receiving the same issues and if they have found a fix so we can work on this together.
Edited by Tuonelan on 5 April 2014 16:01 We have contacted our Customer support team to help you solve your issue.