Constant 90002 Error

I have noticed periodic issues with lag since December.

am having constant 90002 and 90001 too that started a few days ago, I think after the Hatching Tide update. And the errors would come only in the mornings, no errors at night which is weird :/

I have the 90002 error once in the first 10 minutes of logging in and then it goes away until I log off. But it happens consistently every time I play in the first 10 minutes.

I've been having several issues as well. I'm playing on Balmung playing the PS4. It's been so bad that I couldn't get through the first fights in many raids without severe lagging and server boots. The issues have been so bad that it's practically unplayable.

This a bug affects some connections.
When you interrupt the cast with movement 1 or 2 times, PIIIII Error 90002.

Use melee player or tank without cast and u never get this error.

Square need repair this bug.

Unplayable and dont seem to have anyway to fix it.

i hope the maintenance fixes this issue

Constantly getting this too, then I get to go back into the 2000+ queue.. Should be a priority reconnect for someone who just dc'd guys, come on, almost every other MMO has that.

Log in: 1000+ people in q, no worries, I'll wait....error 90002.

Shit happens, let's try again....error 90002.

Another attempt?.....error 90002....

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'm also having the same issue. After I eventually get on. I am unable to do quests because of the server disconnect. (90002)

Getting this error but only when I try to do the story quests. I'm not even doing Stormblood content I'm only 53. Constantly getting kicked off server when i try to continue my story quests. It's ok to have these issues but to continue letting them occur for an entire day? That's a bit much esp for the people who are putting money into your video game. This "early access" should have never been released if your company was not prepared to launch the patch. It's very frustrating to spend so much money and not get whats worth out of it. Again a couple hours sure, but an entire day? Not cool, we pay for that day.

Cannot log in on Cerberus - queue of 1800+, then disconnects with lobby error after a few minutes of being sat in the queue. Reboot game, log back in, queue has increased even more, then disconnects again, repeat, etc.
It looks like it will be impossible to login today.
After the Raubhan mess yesterday, you should be partially refunding subs as this is now 2 days without proper gameplay / any gameplay.
Surely, this will only get worse on the 20th with official release.
SE have been far too greedy and overpopulated each world / server. They must have been able to accurately anticipate player numbers given past experience. They have taken everyone's money without being close to having the ability to let us all play. Refunds, and quickly - we are paying for something you are not providing us!
...oh, and the support service is down, so if you take the time to write a complaint email, it won't process it. Pathetic!

so far since yesterday i have spent more time in queues than actually gaming on Odin...square enix should implement better connection solving...especially when i try to get back online as quick as possible to get the message that my character is still logged on(i have played pretty much all big mmo's over the last 15-20 years and this is the only one where i have had so many disconnects with, i run mumble, discord and teamspeak at pretty much all hours and those never ever disconnects or even get a jump in the latency when this game drops connection on me...

on another note whoever is in charge of server size and stability deserves a foot up their ass for not beefing up the servers for the pre order head start...atm i'm at place 2965 in queue for the server i'm on(Odin)

Dont worry, Im in queue for 30 minutes and there is only 1 person ahead of me. Full server and noone left/DCed/Crashed for 30 minutes. I agree with 90002 and then waiting hour or so to join in. 90002 after 5 minutes of play and 1662 place in queue. I pray to twelve for a lightning to struck people responsible for technical part of this game. Heavensward did not showed them what happens.

i usually get 90002 error and get booted when i try to enter dungeon or instance on duty finder.

Repeated 90002 errors today, I wait in queue as advised by the OF update only for it to boot me with another 90002 again.

Happy early access weekend. :(

almost 2 hours in dungeon queue, finally pops, 90002 lol3000queue Fuck sakes EVERY other mmo has a priority queue for disconnects, why are you guys so shit at simple things like that?

This seems to happen a lot when trying to do instanced content. I'll try and load into it only to get the 90002 disconnect error, then have to fight to log back in and not able to do said instance.

Nothing more demoralizing than waiting 45 minutes for a dungeon queue then getting nothing.

I am not even on Stormblood content yet and I can't advance my class quest because it's an instanced event. Here's what happens.

1. Try to get into instanced event and get disconnected
2. Connect back onto server and wait in queue
3. Game tries to log me in and then kicks me out with error 90002
4. Try to log back in again and go back into an even longer queue
5. Repeat steps 2-4

I guess it doesn't make sense to have separate servers for low level instanced contents but this game is at least 5 years old and this is the second expansion pack so there should have been some anticipation of server congestion. This is nuts!

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!

Quote:

---

Originally Posted by onyxnotfound

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 -_-

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!

Behemoth Server

In game, queued for Frontline

On load Screen, 90006 error

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

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.

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.

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.

Quote:

---

Originally Posted by 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.

---

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.

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?

Please just take this to maintenance.

Quote:

---

Originally Posted by Lammy

I am not even on Stormblood content yet and I can't advance my class quest because it's an instanced event. Here's what happens.

1. Try to get into instanced event and get disconnected
2. Connect back onto server and wait in queue
3. Game tries to log me in and then kicks me out with error 90002
4. Try to log back in again and go back into an even longer queue
5. Repeat steps 2-4

---

Exactly this I haven't been able to login since servers came up on the 16th..
I have patience and have been through far worse launches than this one I'd just feel happier if it at least sounded like something was being done to address the issue .. the stone cold silence is just not acceptable.

Quote:

---

Originally Posted by Lammy

I am not even on Stormblood content yet and I can't advance my class quest because it's an instanced event. Here's what happens.

1. Try to get into instanced event and get disconnected
2. Connect back onto server and wait in queue
3. Game tries to log me in and then kicks me out with error 90002
4. Try to log back in again and go back into an even longer queue
5. Repeat steps 2-4

I guess it doesn't make sense to have separate servers for low level instanced contents but this game is at least 5 years old and this is the second expansion pack so there should have been some anticipation of server congestion. This is nuts!

---

This, exactly for me as well. The only difference is that the amount of time to get back into the game has increased exponentially since the SB launch. That day it took all of 2 minutes to get back in to begin with, later that day it was taking 30 minutes while being stuck in a loop of DCing and logging back in. Today I am almost up to it taking an hour, and while I have completely exited out of everything, apparently my character is still logged in. :(

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.

Quote:

---

Originally Posted by VirtueLol

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.

---

Quote:

---

Originally Posted by Elany

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. :(

Same here, sucks not being able to play.

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 :)

http://imgur.com/ecYYLrd

Yep. I remember this happened in Open Beta and people were stuck in limbo for days. Yay.

Need to set up a day of boycott to basically tell SE fix this or we are done. Right now they don't give a crap and aren't fixing it.

How the hell have you guys not put the servers in maintenance yet? Stop selling the game if you can't even manage your servers. These issues aren't new and have definitely happened before, the shortsightedness and lack of clear direction on how to fix these issues is aggravating at this point. PUT THE SERVERS IN MAINTENANCE/ORDER MORE SERVERS/DO SOMETHING.

The tentative measures that you guys have in place that limit people are ridiculous and not suitable for a game being released in 2017.

Quote:

---

Originally Posted by Daegon

How the hell have you guys not put the servers in maintenance yet? Stop selling the game if you can't even manage your servers. These issues aren't new and have definitely happened before, the shortsightedness and lack of clear direction on how to fix these issues is aggravating at this point. PUT THE SERVERS IN MAINTENANCE/ORDER MORE SERVERS/DO SOMETHING.

The tentative measures that you guys have in place that limit people are ridiculous and not suitable for a game being released in 2017.

---

Already canceled my sub fuck this company