Maintenance for the week of October 5:
• [COMPLETE] ESO Store and Account System for maintenance – October 8, 8:00AM EDT (12:00 UTC) – 12:00PM EDT (16:00 UTC)
• [COMPLETE] ESO Store and Account System for maintenance – October 8, 8:00AM EDT (12:00 UTC) – 12:00PM EDT (16:00 UTC)
The Markarth DLC and Update 28 base game patch are now available to test on the PTS! Read the full patch notes here: https://forums.elderscrollsonline.com/en/categories/pts/
Error 103
stumpy999
✭✭✭
I was just having a play session and had been playing for a couple of hours.
Then I received a crash and a message telling me I was not allowed to play in that zone.
Now I can't log on - error code 103.
-
the answer to 103 is - wait 10 mins yadda yadda
So I can appreciate a load of guys being booted off all trying to log in at the same time causing 103.
However how do I pick up the obscure message booting me off the server, as it seems to me this is the issue not the subsequent mass relog attempt?
Then I received a crash and a message telling me I was not allowed to play in that zone.
Now I can't log on - error code 103.
-
the answer to 103 is - wait 10 mins yadda yadda
So I can appreciate a load of guys being booted off all trying to log in at the same time causing 103.
However how do I pick up the obscure message booting me off the server, as it seems to me this is the issue not the subsequent mass relog attempt?
We have contacted our Customer support team to help you solve your issue.
-
stumpy999✭✭✭lol, just catching up on the forum
and I got a nice mail from the support guys telling me exactly the same as was in the FAQ for code 103.
No mention of why I was booted off in the first place, or if there were any records I could send that may help.
So I got, "you have been booted off for an error"
Yep, lot's of guys had the same and all tried to get on and failed with 103.
"103, please try later, this is traffic related"
One of the key items here, Bethesda, is that you understand the fails. At no point have your organisation attempted to address the root cause of this issue.
I totally get that if 500 guys get booted off and all try and log in that there will be issues.
However, what caused the issue? How can we help you to understand how things crashed in mid-flight? Are there logs, records we can send etc
Please do not send me a another mail telling me I can log on after 10 minutes........... -
ZOS_TristanK✭✭✭✭✭
✭Hi there, @stumpy999. If our Support Team's troubleshooting steps ever fail to resolve your issue, we encourage you to reply to their email. They will always be happy to continue troubleshooting for you. -
stumpy999✭✭✭Let me labour the point
I know I can log in later. (Incident solved, close case)
I know that 103 means busy - ( Recurring incident, problem ticket raised, known issue, workaround in place)
So
What about the actual issue? the one that booted us off? Let's not get distracted by the "getting back on fiasco"
So ZOS
What failed such as to kick me off in the first place? You don't know? Cool, how can I help?
and before you say it, the guys charged with closing tickets and restoring service are not the guys that can answer that
Edited by stumpy999 on June 23, 2014 3:42PM