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

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

[AlbertRedfield]

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

[Kilzjhen]

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

[Kilzjhen]

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

[Sharlyssa]

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

[runeguy27]

Was DCD and still cant get back in

[AlbertRedfield]

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.

[KeyboardFacerollname]

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.

[MistaBojangles]

Having the same problem...

[Bobbly]

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.