Still getting 2002 and 4004 after waiting over an hour in queue after Maintenance

[Mialee]

Fairy in queue from 15h45 to 17h45 est it was better for my got only 2002 once near the end and have keept my place yesterday I got like 10 time 2002 in my 2 hours queue to log in

[Rae88]

Fairy in queue from 15h45 to 17h45 est it was better for my got only 2002 once near the end and have keept my place yesterday I got like 10 time 2002 in my 2 hours queue to log in

Today was the first time I didn't get kicked out of queue so definitely better

[RinaB]

I shouldn't have to wake up at 4 am for a couple hours of msq because I know after work it's not even worth trying. This problem is going to persist for a lot longer then people think and I would at least like to transfer to a very low pop NA server if there even are any.

[Myrany]

I shouldn't have to wake up at 4 am for a couple hours of msq because I know after work it's not even worth trying. This problem is going to persist for a lot longer then people think and I would at least like to transfer to a very low pop NA server if there even are any.

My Server (Zalera) is one of the lowest pop NA servers and to be honest it isn't any better for us. No major queues early in the morning but by 10-11 AM Central time it is starting to back up. By noon hang it up and it doesn't get better from there.

[LegendWait]

I got 90006 right at the moment the maintenance started and I was doing an expert roulette. Dont know why that happened since I was already in an instance duty

[Faafetai]

I got 90006 right at the moment the maintenance started and I was doing an expert roulette. Dont know why that happened since I was already in an instance duty

Being in an instanced duty I believe does not matter. Before acquiring a vpn I would get kicked from duties no matter what content I was in, given this was when the player volume was slightly lower so even with a 500 person queue that just meant a few minutes maybe even seconds in a queue before getting back into the duty. Though I wished there were a system in place for priority queue for those in an instanced duty as to not get a penalty due to ntt nodes not handling traffic properly or the servers buckling under the weight of server load. I am sorry you got booted from your duty.

Even with a vpn now, the issues are all back from a few months back without the vpn and I am wondering if it was not the servers all along.

After maintenance I did notice my position in queue being saved, but unsure if others are experience this as well. I logged in early morning 8am est got booted by 90006 error logged back in waited an hour in the small 500 something queue to finish my cut scene when picking up sage. Went to attempt to warm up in palace of the dead because I didn't want to get booted from a duty and was booted during the second floor attempted to log back but 1500 in queue and I knew it would be pointless.

So.....I attempted anyway for science and found out around 500 in increments that each 500 is about an hour of wait time. I started in queue at 3pm est #2169 ended after two disconnects at around 5:47pm est.

This could just be placebo but the queue wait time is way longer than it use to be. Before 500 in queue meant only a few minutes in queue where now it is guaranteed to be an hour. I don't know if it just a number reporting wrongly or something else, but it is just a strange something I noticed.

[Hasrat]

I'm gonna take a wild guess and say "keeping your place in line" could very easily result in just as many errors. The server is crashing to save itself from catastrophic failure. Saving your place in line would just mean more crashes while the server panics about how to handle the excessive load.

I could be way off here, it could be something else entirely. But, typically, when you've got something that seems "so obvious, why haven't they already done this?" It's because they've already thought of it, too, and it doesn't actually work the way people think it would.

Whatever the case, it takes time to diagnose, develop, and implement solutions. Working out how to get a band-aid fix operational just takes time and resources away from actually solving the problem itself.

[Mika_Zahard]

They said today that at around 4:40am PST they did maintenance on the log in servers to fix the issues with people in the queue getting booted with 2002, 4004 and the 3001 errors.

Well, it isn't fixed. Already was in a queue just under 5k, got down to around 1500 after an hour waiting and got a 2002 and now am back at 4800 in line again...

I get they said that this is a hard one to test, but i can confirm it is still doing it.

Square, please look into somethign that can keep our place in line when we disconnect and give us ample time to sign in. When i get disconnected i cannot log back in right away all the time due to repeated 2002 error before getting back to getting the character select screen. MAC and IP addresses should be sufficient to store our place in line for at least a few minutes at a time before removing us.

Same, i was in a 5100 queue and went after 90 minutes into 1600 position, then immediately 2002'd and got placed back into 5600.

TY Square