10102

Damn, these errors just keep on coming. When will SE catch a break lol.

Happened again its instances and duty finder... Gonna crash everytime.

Sigh.....got booted after doing lvl 20 LNC quest, then got 10102 and 90000 errors, got back in, booted again and same. Took about 20 minute to get in the third time. Will see what happens next. :(

im not mad or really irritated with square. im morely just tired of the interruptions

It is really getting to an unacceptable point now...

Same here. Joined DF on Balmung and now I have 10102.

Uveck Lord

No end in sight... 90000 to the 10102 on Lich...

So, I guess there will be another emergency maintenance soon... I agree with DarkHades 100%

Give it time, it actually corrects itself. Took 10 minutes for me to reappear and relog back into the game.

seems pretty wide spread now. Que on malboro went from 10-20 up to 280 now after the kick.

i have been pretty patient about things since beta phase 4, i'm close to raging over this stuff though, i lost out on most my vacation time i took off to play, i can't get that back no matter how many free days they throw my way, they do maintenance the only time i am awake yesterday on my only day off all week, and now i'll probably get locked out of playing tonight with the luck i have been having. fml

10102 at tam ....

im stuck in darkhold :/

90000 exiting from Praetorium (into I assume quest area)....10102 when I try and relog

90k entering Sastasha, 10102 trying to get back in-game.

It's always one thing or another, huh.

Here we go again...

Sigh, just got me while trying to do Amdapor Keep.

I don't understand how these errors never popped up in beta....when that should have been the first place they showed up.

Not even in an instance..just following my story quest and got 90K...been trying to log for about 15 minutes now and getting 90K and 10102...

In square enix's post on the patcher you see that in the duty finder all the world were separated into groups.

*North American/European Data Centers
-Group 1
Adamantoise / Balmung / Cactuar / Diabolos / Exodus /
Goblin / Hyperion / Lamia / Malboro / Moogle / Odin /
Ragnarok / Siren

-Group 2
Behemoth / Cerberus / Coeurl / Excalibur / Faerie /
Gilgamesh / Leviathan / Midgardsormr / Phoenix /
Sargatanas / Shiva / Ultros

If you look at everyone posting in this thread they all come from NA/EU group 1. All the servers in group 1 most likely will experience maint. Coming up soon. Even so, a lot of people have been able to get in after trying to log in numerus times. My advise is to not que for an hour and try again then. Or watch for updates for our Duty Finder group.

Quote:

---

Originally Posted by BTizzo

Not even in an instance..just following my story quest and got 90K...been trying to log for about 15 minutes now and getting 90K and 10102...

---

you prob were bout to go into or coming out of a instance mission. the instance servers are still all F'd up it seems

Quote:

---

Originally Posted by Yuumerz

In square enix's post on the patcher you see that in the duty finder all the world were separated into groups.

*North American/European Data Centers
-Group 1
Adamantoise / Balmung / Cactuar / Diabolos / Exodus /
Goblin / Hyperion / Lamia / Malboro / Moogle / Odin /
Ragnarok / Siren

-Group 2
Behemoth / Cerberus / Coeurl / Excalibur / Faerie /
Gilgamesh / Leviathan / Midgardsormr / Phoenix /
Sargatanas / Shiva / Ultros

If you look at everyone posting in this thread they all come from NA/EU group 1. All the servers in group 1 most likely will experience maint. Coming up soon. Even so, a lot of people have been able to get in after trying to log in numerus times. My advise is to not que for an hour and try again then. Or watch for updates for our Duty Finder group.

---

This is happening on hyperion as well

Quote:

---

Originally Posted by Kahne

This is happening on hyperion as well

---

Your server is in group 1 like i said.

Same situation here. Just got entry through Duty Finder and d/c with error. Can't log in back :(
Probably Duty Finder server charshed? Originally from Moogle server.

Used duty finder with one other groupmate for Toto-rak.
Took forever to load into instance, and eventually went to 90000.
All subsequent logons generate 10102.

Groupmate made it in OK after a long delay as well.

Rhaine Shayde
Hyperion

Edit: Able to log into my character on Goblin world. However attempting to log back into Rhaine throws 10102 still.
Edit2: About 30 minutes later I loaded back to my spot in the world before the failed zone into Toto-rak. The dungeon instance I was supposed to be sent to was still ongoing (I had thought my ability to logon might be tied to it - but I guess not).

Yep, same here. Was doing a story instance and I was thinking to myself, wow this is the first FF I have really liked in over 12 years. Right after that thought I got hit with a 90k crit, a 3102 finisher and then a 10102 rez sickness. I know that was horrible, but that is what it felt like lol.

Same here for Halatali, 90k>3102/10102

Quote:

---

Originally Posted by Riv

I don't understand how these errors never popped up in beta....when that should have been the first place they showed up.

---

These errors are related to stresses placed on the various servers due to the enlarged playerbase. Beta showed no where near the same numbers of players since launch, and as more people join the numbers will keep rising...thus stress builds (you can only put so much weight on a bridge before it collapses)

same thing happened to me, same instance too

Same error.

Illyria Knotfred - Diabolos

happened 3x to me in the last 45 mins...

Super Teemo
Server: Goblin

All of the above exiting Stone vigil.

Same on Cactuar
30 min now after i tried to do my personal story

Kicked out on Cactuar when joining an instance. I started a new character on a different server and got in fine. Watched the cutscenes and logged out once I regained control. Returned to Cactuar character and it worked fine. Worth a try I guess.

Qued for Ifrit, load took forever only to kick me from the game, now i cant get back on :mad: guess ill just go take a nap :(

Quote:

---

Originally Posted by Velox

These errors are related to stresses placed on the various servers due to the enlarged playerbase. Beta showed no where near the same numbers of players since launch, and as more people join the numbers will keep rising...thus stress builds (you can only put so much weight on a bridge before it collapses)

---

Yes but we were supposedly "stress testing" in beta. Maybe they didn't let enough players into the beta. I honestly never had connection issues from Alpha to Beta 4. You would think with the data they got from those tests that they could more accurately anticipate problems that would arise as more players joined.

But I guess it's water under the bridge. I just like to complain.

I cannot hold my patience already... Im still encountering 3102 and now its getting worst 10102...

Server: Cactuar

FFXIV ARR: 1017, 90000, 3102, 10102

I think I just summarized this weeks play experience in one line...

I really enjoy playing this game. The problem, however, is not being able to play. We just went from no queues and error 1017 to queues and errors 90000, 3102, and 10102. I really hope the devs actually fix this broken game (yes, it IS broken if you can't play due to server issues). I want to be able to subscribe to this game. I wanted to play tonight. I couldn't. This is not the first night I couldn't play when I wanted to. I am not paying good money for something I can't use. I refuse to pay for services not rendered. If the game is not fixed by the time my 30-day trial runs out (I paid for CE), I will NOT subscribe. Is it a waste of $39? Sure. However, subscribing would only waste even more money.

So far I will NOT be subbing after my 30 days is up SE. This is just sad.... getting 90k 10201 3102....all day long.....FIX YOUR SHIT....when your the only game to have come out in like 6 months its usually best to expect EVERYONE to play it since its the only thing on the market ATM all your doing is killing yourself subs the thrill dies very fast when you get kicked after waiting in duty finder ques for hours to errors that have been around since BETA....

10-102 (like 3-102) is a generic error code. This code is for character still in duty service.

It is likely not the same cause of the issue, but certainly causes the same symptoms. Its a new duty service.