Constant 90002 Error

[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.

[ZediaAkula]

Been a FF fan from the very first one (yes, I'm that old). Played FFXI until FFXIV: ARR came out. Would still be playing XI except no console support. After the experiences of the last two days, paying for early access and getting nothing but headaches, not sure if my loyalty is worth the stress. This is supposed to be a fun game, not a nightmare.

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.

[Ryshel]

Please just take this to maintenance.

Yes, can we please just get this fixed? "Cold Steel" and the one not long after with Pipin as the quest NPC are not the only bottlenecks anymore. "Doing something else and coming back later", while a frustrating response, would be viable if not for the fact that it doesn't work at this point. Not only are most MSQ instances becoming bottlenecked but we can't even do roulettes or dungeons or ANY instanced content now. Any attempts at anything result in 90k errors from the attempt to enter the instance, followed by endless 90k and other errors for at least an hour to two hours straight, often longer, at any attempt to log back into the game. I'd rather have zero access to the game for a time with the guarantee when it comes back up that I and my friends will be able to progress without further issue than to keep getting just a little further and then stuck for hours.

[toussaint89]

This won't be fixed till people A. stop playing the game. B. SE takes down servers for 2-3 hrs to beef up the servers. People are getting constantly disconnected cause to many people are in that instance and it kicks people out. But, don't expect SE to do option B. They basically told us oh well deal with it.

Also, this well also get worse come the 20th so yeah. GG SE