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

As title says, I dared to do the SAM solo duty, and was kicked out of server. Trying to get back in, only to meet with this error. Is there a way to fix or bypass it?

Quote:

---

Originally Posted by MardukAlvitr

As title says, I dared to do the SAM solo duty, and was kicked out of server. Trying to get back in, only to meet with this error. Is there a way to fix or bypass it?

---

I too have this exact same error when I attempted to SAM solo duty for lvl50. Keeps giving me error when I attempt to login, but another character seems to be fine, as friends that are on the same server are also able to login

Same here. Just gonna wait or spam it for 10 minutes ish. It will let you back in eventually.

Basically we are all screwed on MSQ instances and are stuck in the story because of this. Enjoy.

Ummm more like hours or a day for some ppl and still not able to get in

Was DCD and still cant get back in

It will let you back in after however long the instance you went into. It must have something to do with the instance and the congested servers right now, to the point where it tries to log you back into the middle of the instance but can't because of the "stress", so then it waits for you to get kicked from the instance after the time limit runs out.

The problem may be that your main character might still be considered "logged in".

I was recently DCed trying to enter PotD and couldn't log back in(I'd get through the queue and to the loading screen and then booted out with a "Connection to server was lost" message).

I logged in on an alt and saw that this character(Stoic Nod) is still logged in.

Having the same problem...

I too have been experiencing this same issue with a number of solo instances. I have had to wait 30 minutes for the auto AFK kick to boot my character off before I could log back in.

Having same issue here, got disconnected while joining an instance and cant log back in due to 90002 error

Looks like I can't do my 54 level Ninja skill quest either, kicks me out if I try to start the 'instance' part

i've been stuck for nearly 40 minutes trying to get back in after trying to do Palace of the Dead. this is getting to be utterly inane. this is past being just an inconvenience. this is to the point of being stupid to the point of "why am i playing this again?"

I've been trying to get Past the Pipin Part of the Storyline for over 24 hours, trying for an hour, going and doing palace, running a few times, getting kicked out, takes an hour to get back in and then..then huzzah, try pipin again...then PotD...yeah. 24 hours is bad.

Actually all instance servers suffer! -- Was light farming cause the father-son wall was too great to bear, then the PF groups got a BSOF (black screen of fail -- sibling to the BSOD - blue screen of death)

Don't know how they havnt fixed this I've spent more then 50% of my time trying to play D/C or in a queue

Quote:

---

Originally Posted by ghostlead3r

Don't know how they havnt fixed this I've spent more then 50% of my time trying to play D/C or in a queue

---

Its not a matter of how they havent fixed it, its a matter of why, and the answer to why is the how, as such its because this is a temporary issue that will resolve itself with time. -- Working as Intended

"Working as intended" shouldn't be 90King people trying to log back in. this is not a solution. this is a big issue.

I'm getting this issue as well. I finally got a pt (loldps queue) for the first new dungeon, and dc'd while moving to the instance. 90002 every time I've tried to get back in for the last hour. I guess I'll play again tomorrow. =/

Quote:

---

Originally Posted by zXr

Its not a matter of how they havent fixed it, its a matter of why, and the answer to why is the how, as such its because this is a temporary issue that will resolve itself with time. -- Working as Intended

---

No, I think not.

Throttling those instance quests would be fine it just said hey you can't do this come back later. When it's kicking you out and locking you out until it times out that's another matter.

for the past three hours i have been trying to get back into game after a 90k "connection to server was lost" try to get back in .... in que of 500 or so... work my way through the que only to finally get to the front of the line to find another 90k server lose even before fully loaded in game.

Faerie server
PS4 user

Stuck in an endless loop now when I tried to get into Snowcloak as a healer to help those who are dps doing it or have never done it before. DCed right away and now can't get back in.

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.

Thanks very much for your comments!

Judging by those on my friends list with this problem, it does indeed look like it has something to do with your character getting stuck online inside the instance even though the actual player isn't even in the game anymore. I see them online and in the location where they tried to enter the instance, but they don't even have the game open.

So it looks like the information that the player has disconnected never gets sent to the instance server and isn't closing it like it should.

Quote:

---

Originally Posted by Jasonsama

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.

---

This is exactly what's happening to me also. Simply replying to add myself to the list of people affected by this. It's one thing to trickle people into an instance to mitigate congestion, but I can't even spend my time doing something else.

Very disappointed.

This is happening to me as well. I've restarted my router, did a speed test which came back normal. I'm not even in the new content. I'm only level 25 and am trying to do the main story so this is beyond annoying.

Same happens with level 51 MSQ. 90006 error and then im unable to log back in. Says "invalid password" I have to change my password to get back on and then about a 15-20 minute que. Get back in and kicked instantly. Rinse and repeat

Same issue here. Got fed up trying to get past Pipin and went to do 50 RDM quest. Got disconnected. Tried to get back in, got 90k errors for half an hour, went to take a nap. Came back, loaded in went to do RDM quest again out of hopefulness, disconnected again. Constant 90k errors despite waiting patiently in logon queue (not trying to cancel and force my way in).

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

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.

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!

Stuck too was in PVP and got kicked.

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.

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

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.

Quote:

---

Originally Posted by Jasonsama

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.

Quote:

---

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

---

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

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

Quote:

---

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

---

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.

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