Error 5003

[Lenicus]

Server: Excalibur and Duty Finder
Player: Lenicus Tramoria
Player: Durzo Blight
Player: Suga Babe
Player: Tiberious Dovahkiin

Issue: Error 5003 Authentication error causing boot due to loss of server connection.
Details: Boots out to desktop completely on PC as well as kicks to restart on Playstation console.

All players listed above have had disconnects throughout day both in regular gameplay and in duty finder.

[TreyZerODM]

Error 90000 and then immediately following Error 5003

Server: Balmung
Players: Sierraleone Valrose, Trinitine Teppe.

Disconnected due to Error 90000 and then same as above.

[CrimsonQueen]

Server: Excalibur
Character: Crimson Queen
Same thing as above, three times today, I've never had any problems like this before.

[ftw2177]

after patch 2.05 have had two DCs, also have multiple reports of 5003 DCs within my free company. As far as my issues though got DCd during fishing with a 90k which kicked me to launcher for a 5003 message, second DC was a total game failure, kicking me all the way out to PS3 menu, no error messages just closed ffxiv and returned to XMB. Hoping SE will remedy and get another hotfix in the works. Wish there was some way for these software companies/developers to pre-test patches before they release them. It seems more and more these days they just release them and fix them after players get to do the testing.

[Velev]

Love how people jump onto the forum when they have a prob and just create their own thread, instead of taking 2 minutes of their time checking if one already exists....

Point being, instead of having let's say 20 threads spread out all over the place of the same issue, one big thread is more effective in case you're trying to get your point across to the devs or whoever...

Just a thought..

http://forum.square-enix.com/ffxiv/t...0000-then-5003

http://forum.square-enix.com/ffxiv/t...0pm-Eastern%29

[Boretalith]

Greetings,

We understand that you are experiencing difficulties with error code 90000. There is already an open discussion regarding this same concern here. Please browse through this thread for any possible solutions you may not have tried yet. In an effort to consolidate information on this error, we ask that any additional information you gather be added to that thread. As such, we will be closing this particular thread. We apologize for any inconvenience. Thank you!