90002 Error - Kicked out after entering a duty, unable to log back in

[Araahaiel]

For all the people saying this is only early access this is impacting and disconnecting people just doing old content and trying to just play. So people who don't have the expac are still impacted by this error so hopefully it is a high priority to be fixed!

[shawnaus17]

Stuck too was in PVP and got kicked.

[zXr]

How many times do i need to post this, there are three main servers we deal with when playing, Log-in, World and Instance. The log-In and Instance servers are data center based servers, which means everyone on Primal uses the Primal servers, everyone on Aether uses the Aether ones, currently due to the crazy congestion created by millions of players trying to access the data center based servers, they are crashing or going offline. To 'fix' your character the servers need to be physically restarted so they can be logged out safely and successfully back to your world server.

They will not proceed to restart the instance servers until its determined EVERYONE who is currently inside is 'stuck', they need to allow time for those who are in running instance to finish, needlessly restarting serves to release a fraction of a percent of the population while dooming those who have gotten in will make the MSQ gated instance take longer.

[Biskitlicious]

Yeah...i can't even log in and i was not in an instance, and was nowhere near SB areas, i was in horizon just chilling and getting 90k errors

[Stash420]

Entered my level 45 job quest, dc'd with a 90002. Sat through a 750 person queue, error 90002 while logging in. Sat through another 770 person queue, error 90002. This is starting to get a little ridiculous.

[Tempete]

Also voicing the 90k bug has gotten me in a loop.
Gilgamesh server, queued for PotD, kicked, wait in queue to log into the world through a roughly 3000 queue, which is around 30 minutes, kicked upon logged in. Repeat indefinitely. Best early access ever.

I did the same thing. Queued up for PotD, it popped and then BAM! Lost connection. Thankfully, I don't have THAT big a queue, only 600ish to sit through but I still can't log in and it's really not enjoyable at all. I just wanted to play after coming back home.

[WhiteFalk]

How many times do i need to post this, there are three main servers we deal with when playing, Log-in, World and Instance. The log-In and Instance servers are data center based servers, which means everyone on Primal uses the Primal servers, everyone on Aether uses the Aether ones, currently due to the crazy congestion created by millions of players trying to access the data center based servers, they are crashing or going offline. To 'fix' your character the servers need to be physically restarted so they can be logged out safely and successfully back to your world server.

They will not proceed to restart the instance servers until its determined EVERYONE who is currently inside is 'stuck', they need to allow time for those who are in running instance to finish, needlessly restarting serves to release a fraction of a percent of the population while dooming those who have gotten in will make the MSQ gated instance take longer.

That's very reasonable and all but it doesn't stop resentment and angry people are unreasonable people.

There are a few temporary strategies they could implement to help the congestion without impacting the whole server and one of them is to adjust the AFK timer.

What has been happening is that people sometimes enter an instance and immediately gets logged off. But the problem is that their character remain in the instance and registered as AFK, in essence getting stuck in limbo while the player themselves are logged off. So when they try to login with that character they are unable to because while the server registers that the player is logged off, the character is in a sort of AFK mode and won't be released from the instance until the AFK timer (30 mins) runs out, the instance timer runs out or your party members kick you; whichever comes first. Problem with the battle instances is that you don't have the third option of having your party members kick you. As a result you're unable to login until one of the timers run out (or you die in the instance) but worse still is that your character is probably hogging the instance as that is happening and preventing other people from going in since you've taken up the quota.

For these periods of high congestion I think it is fair enough for SE management to adjust the AFK timer from the 30 mins to 10 or even 5 mins. If you're going to AFK in these busy times for so long, you can log back in when you're ready to play. This way instances can be freed up much faster in the event that people get dc. Also lets people log back in much faster instead of getting endless 90002 errors...

[AethValar]

Same issue. Been stuck in this error 90002 loop for over an hour.

[zXr]

Yeah...i can't even log in and i was not in an instance, and was nowhere near SB areas, i was in horizon just chilling and getting 90k errors

The expansion content isn't the issue, its the instance servers specifically, were you using the data center servers in any capacity? Duty Finder? Party Finder?

I have heard about players getting locked out with the 90k;s just for using those systems over the past 2 days, when their instance popped or someone joined their PF group. Those who were doing neither on the other hang and have had it happen, that I do know about, have players from other servers on their blacklist, a thought occurs with the ground-work set for cross-server friending now, there could be a connection.

[Biskitlicious]

Yeah...i can't even log in and i was not in an instance, and was nowhere near SB areas, i was in horizon just chilling and getting 90k errors