Getting same error over and over again, please help.

[Lakhan]

i keep getting same error over and over again. it starts with a r0 and the error window pops up at the same time. i drop back to lobby and not be able to log back in for 2-3 mins.

this is the error message i get:

An error has occured on the game server.
(30002)1214049860,19175888,5

i don't know what does that mean of course. if anyone having the same or a similar problem, please feel free to discuss it here. and it would be better if someone has any idea what that is and what causes it.

[tymora]

It would be nice if SE can post on Lodestone all of the possible error codes in the game.
It will probably free up a lot of SE resources when players can do more in-depth troubleshooting.

[Aerycat]

It happened to me once, but then again my connection was down and got DCed. It's showing this somewhat 'misleading' error however... I can for sure remember it's 30002 but the rest, I can't say Probably due to the occasional instability on the connection ?

[Geesus]

Try and just restart ur PC. And try and take notice of when it occurs and how frequently. Usually when you get that error, you need to completely log out of XIV back to your Desktop and then relaunch the game. Good luck.

[Zenaku]

30002 error i thought that mean D/c from server that happen a lot in beta meaning the game was still not up don't know if that what it still mean but that look like internet d/c to me.

I think you may be having packet loss issue are you on wireless.

[Steggun]

As far as I can tell it's an issue on SE's end, I have been getting (30002) errors ever since patch 1.18. At first it was happening 10 or so times a day now it's down to 2-3 a day but still a major pain in the ass when it happens in the middle of a dungeon run or leve >.<


http://www.youtube.com/watch?v=JYc05gZFly0

[Danavia]

I just tested my connection and I'm getting 0% packet loss... pretty sure this all started after the latest patch, never used to get this annoyingly frequent error.

[Frein]

30002 is definitely a connection loss error. Some people report they've only been getting it since the latest patch, so it could be a bug in the game causing it.