Constant 90002 Error

[Tavira]

These people knew this was going to happen and yet they do nothing about it. Seriously there should be instances for all places in this game when they know that servers will be congested, or better yet get more damn servers cause I know they can afford them! This shouldn't be happening to a game like this!

[DanLeMan]

I started the first quest (arena) after obtaining the SAM class when I got D/C and upon login always get the 90002 error.

EDIT 1: Was finally able to connect.
EDIT 2: Now I'm getting random D/C with 90002 login errors.

I basically have the same issue with the same quest. Whenever I try to log back in afterwards, I get the error again and I'll have to wait 10-20 min till I can successfully log back in. At this point I'm forced to grind fates with the new jobs till they fix this freakin instance issue -_-

[VirtueLol]

Yeah stuck in the 90k loop. Probably time to contact Amazon for a refund, I'd be more patient if they were actually taking the servers down for emergency maintenance or at least acknowledging NA's problems beyond, "please wait lol." 95% of the content is gated behind a solo instance that you have a .00001% of successfully accessing. Servers haven't been brought down for maintenance once. Characters potentially inaccessible until the next client update (lmao). Reporting this to GameSpot, IGN, Polygon and Kotaku...hopefully they can get the word out: DO NOT BUY STORMBLOOD!

[Deceptus]

Behemoth Server

In game, queued for Frontline

On load Screen, 90006 error

On relog constant 90002 error, can't access character.

[MissD34th]

Same, went to do a solo mission and was kicked out of game. Now stuck getting a 90002 error when I try to load in.

[Dyvid]

SE, you have to remove the damn solo instance fights from MSQ to fix this problem. This whole sit and wait 10 days while 6 millions players goes through the quest is an insult to your customers. Quit dragging your butts on the carpet and drop a patch tonight that fixes this problem instead of trying to "improve" you DF server. You're trying to fix a water leak with rice paper.

[ZediaAkula]

DF popped for the Shisui of the Violet Tides dungeon. Before the CS started, I was booted from the server. So I log in, and wait through the 500+ players in queue... and it tries to load me in the dungeon again but kicks me with the 90002 error. I can log into my alts on the same account (after waiting for the other 500+ players to enter), but I can't on my main...she's stuck in that CS. I have no way to get her out. It's not like I'm getting 90002 as I'm running around doing stuff, as I said, I can log into my alts but because my main is in the CS/dungeon, I can't log in.

Is this what this discussion is about? Is there any way to log her out of that dungeon? Never had this problem, so I'd appreciate help.

[VirtueLol]

DF popped for the Shisui of the Violet Tides dungeon. Before the CS started, I was booted from the server. So I log in, and wait through the 500+ players in queue... and it tries to load me in the dungeon again but kicks me with the 90002 error. I can log into my alts on the same account (after waiting for the other 500+ players to enter), but I can't on my main...she's stuck in that CS. I have no way to get her out. It's not like I'm getting 90002 as I'm running around doing stuff, as I said, I can log into my alts but because my main is in the CS/dungeon, I can't log in.

Is this what this discussion is about? Is there any way to log her out of that dungeon? Never had this problem, so I'd appreciate help.

You have to wait for the instance to expire sadly dude. It's a dead instance now and everyone else who you were going to be partied with is having the same issue.

You see, normally what competent developers do is they whip out their back-up server blades and expand the instance servers for the first couple weeks of launch. SE on the other hand...just wants you to wait it out.

[AlphaOne]

Try to do lvl 64 msq instance get booted from game, spend 30 mins trying to log back in well getting constant 90k errors. Maybe bite the bullet and put game down for emergancy maintenance. As it stands unless this is fixed soon will seriously reconsider subscription, and will not be recommending stormblood to friends. Worst of all is weak apology yesterday then total silence on issue. So 2 questions for anyone from Final Fantasy 14 team:

1. When will this be fixed? And asking community for patience is not acceptable anymore.
2. What will you be doing to compensate people who pre-ordered for early access that you can't deliver or are refusing to take responsiblity for and fix?

[Elany]

Please just take this to maintenance.