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

[ChillbroSwaggins]

Yeah, mine happened well over an hour ago on Coeurl. I just didn't have a mind to check the forums and just chalked it up to new release blues. Heavensward wasn't even this bad, and at least they stress tested for a solid week before hand. This is just getting crazy now. It'd be one thing if I could still play and a quest was borked, it's another to not even be able to log in while the servers are still up and operational. I'm thinking they might have to take the servers down and do an all-worlds maintenance to sort this one out.

[Nabian]

I had the same issue while working on level 64 MSQ. After watching the cutscene i lost connection and am unable to log back in. After waiting in que I get disconnected with a 90002 error when the que reaches 0.

[Newbcake]

Unable to join any duty dungeon. This is a serious issue that they need to figure out.

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

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

[zXr]

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

Yeah, agreed they need to tighten the AFK timer, however as you said there is this instance of desynch occurring: World server reports offline and instance reports online, this desynch is worsened by the congestion... The quickest 'fix' I would think is for those who have alternate characters or the capability to make another character, would be to get on that one and post an in-game ticket, GM's have the power to move 'stuck' characters from server to server.

[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

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