Error 10102 - Please Post Name, World, and Current Zone

[KrypticAvox]

Name: Kryptic Avox
Server: Cactuar

[kxz]

Name : Dues Mortis
World : Ultros
Zone : East Shroud

[Garbo]

Marlo Stanfield
Excalibur (Legacy Character)
forget zone

[Exocrypt]

Name: Exo Valdayus
Server: Ultros

[Veriz]

I also had error 3102 while loading into copperbell mines in beta 4 and have now had error 10102 all this morning.

Name: Veriz Alkoz
Server: Behemoth
Zone: Copperbell Mines?

[LuckyMojoKingsly]

Name:LuckyMojo Kinglsy
World:Moogle
Zone:Copperbell Mines

[Chrysus]

Mojo19906
Name: Chrysus Bu
World: Cerberus
Zone: Southern Thanalan Ul'dah

I was lvl 24 when this happened

Either a 3102 or 90000 error and booted out. Now a 10102 connection with the server was lost as I try to log back in

[Craik]

Craik Menderan
Balmung
Central Shroud

I never received error 3102 in open beta. I was not on except for a little the first and last day though. I received error 90000 while going from New Gridania to Central Shroud. This happened about 10 minutes after finishing satasha. After that the NA/EU world list would not show up for about 10 minutes. Then, I started getting error 10102 every time i tried to log in.

[Rixusaku]

Name: Rixusaku Zoxus
World: Gilgamesh
Zone: Western Thanalan

I was getting error 10102 and 90000 before the NA/EU servers went down for their emergency maintenance after the Gilgamesh and Excalibur worlds had emergency maintenance done on them. I was just questing when it booted me out.

(Their timestamp for the mass worlds emergency maintenance is: Aug. 24, 2013 from 3:00 p.m. to 5:30 p.m. (PDT))

[Dojah]

Name: Dojah Khomaht
World: Adamantoise
Zone: Central or Western Thanlan

------------

*Details of note**
- I DID have a chance to log into my character after the Open Beta 3102 error was fixed.
- I was NOT logged out in an instance when I began having this issue. I had just entered a new zone in Thanlan when I decided to log out, and then log back in to fix a sound issue. Upon attempting to log back in, I began receiving the 10102 error.