- Open the client, either through launcher or directly through the .exe
- Type in your username and password, do not hit enter and do not click login.
- Open this url in a new tabhttps://live-services.elderscrollsonline.com/announcement/message?announcer_id=2
- If it times out, keep trying.
- When it opens and you see
<?xml version="1.0" encoding="utf-8"?> <zos_platform_response><response><message></message></response><result_code>2000</result_code><result_message>success</result_message></zos_platform_response>or something similar go back to the client and hit the log in button.
It should log you in without error.
- Open the client, either through launcher or directly through the .exe
- Type in your username and password, do not hit enter and do not click login.
- Open this url in a new tabhttps://live-services.elderscrollsonline.com/announcement/message?announcer_id=2
- If it times out, keep trying.
- When it opens and you see
<?xml version="1.0" encoding="utf-8"?> <zos_platform_response><response><message></message></response><result_code>2000</result_code><result_message>success</result_message></zos_platform_response>or something similar go back to the client and hit the log in button.
It should log you in without error.
It worked. But why?
- Open the client, either through launcher or directly through the .exe
- Type in your username and password, do not hit enter and do not click login.
- Open this url in a new tabhttps://live-services.elderscrollsonline.com/announcement/message?announcer_id=2
- If it times out, keep trying.
- When it opens and you see
<?xml version="1.0" encoding="utf-8"?> <zos_platform_response><response><message></message></response><result_code>2000</result_code><result_message>success</result_message></zos_platform_response>or something similar go back to the client and hit the log in button.
It should log you in without error.
It worked. But why?
wolonggong wrote: »Error 200 is NOT a client side issue, it IS a server side one.
Proof?
I am also getting error 200(7:4:178:597) on BOTH my PC and gaming laptop when trying to connect to the NA server and have been getting it for about 30 minutes now...however, if I switch over to the EU server I connect immediately.
That makes it server side. In fact, my Nephew that lives in the same town as me has the exact same issue, on two different PCs, and can connect to the EU server.
There, 3 different PCs and a laptop, all the same issue only with connecting to the NA server. I am right outside Chicago.
wolonggong wrote: »Error 200 is NOT a client side issue, it IS a server side one.
Proof?
I am also getting error 200(7:4:178:597) on BOTH my PC and gaming laptop when trying to connect to the NA server and have been getting it for about 30 minutes now...however, if I switch over to the EU server I connect immediately.
That makes it server side. In fact, my Nephew that lives in the same town as me has the exact same issue, on two different PCs, and can connect to the EU server.
There, 3 different PCs and a laptop, all the same issue only with connecting to the NA server. I am right outside Chicago.
Are they really not gonna acknowledge this as a problem? There have been mods on yesterday deleting and moving threads. So they have to have seen this issue! This is just pathetic customer service.
If the problem is server side (forgive my ignorance), would it not be effecting all players on PC/NA? I've had no trouble logging in yesterday or today.
LadyJohanna wrote: »Disabling both addons has allowed me to log into the game reliably and without issues, every time, since the reinstall.
VirtualElizabeth wrote: »I wonder if they need to buy new servers or they had hardware failures that is decreasing the available log ins.
First, a player should always use the Launcher's Game Options menu to Repair Files after the client crashes or the connection with the host server is lost. When the game client "exits" without closing any and all files that it had opened, there is the risk that the files will be damaged. So you can expect an Error 200 dialog if the files have been damaged after a crash.I've seen it numerous times on the forums. Error 200 as of today has been common. Logging in after being kicked, or a crash or just launching the game will give you error 200 and you cannot log in, no matter how many tries you do.
This is the only fix I know of currently. However, if you find out another one please post it.
Run repair from the launcher. See below. It takes me about 5minutes. (I've done this 3 times today, once a crash happens I get the error again.)
( image deleted )
Hope this helps!
Nice, the group finder still doesn't work and now I can't even log in. Was kinda hoping this game was a bit less janky after my 10 month break... I want to love you, ESO, but you gotta work with me here.
Shadowshire wrote: »First, a player should always use the Launcher's Game Options menu to Repair Files after the client crashes or the connection with the host server is lost. When the game client "exits" without closing any and all files that it had opened, there is the risk that the files will be damaged. So you can expect an Error 200 dialog if the files have been damaged after a crash.I've seen it numerous times on the forums. Error 200 as of today has been common. Logging in after being kicked, or a crash or just launching the game will give you error 200 and you cannot log in, no matter how many tries you do.
This is the only fix I know of currently. However, if you find out another one please post it.
Run repair from the launcher. See below. It takes me about 5minutes. (I've done this 3 times today, once a crash happens I get the error again.)
( image deleted )
Hope this helps!
Second, Repair Files has never done anything that enables me and many, many others to log-in to play the game without receiving an Error 200 dialog instead. There is nothing wrong with the files.
If you did not receive the Error 200 dialog after starting the Launcher and using the Play button (or after using a shortcut to launch eso.exe, or eso64.exe), followed by entering your account name and password to log-in, then you have not encountered the problem that we have been reporting. Your "fix" is not a "fix" for the problem, but for another one instead.