I've been bitten by the 3102 error

Sometimes, apparently, the server doesn't register that you've logged off if you DC while zoning. (!)  This happened to me last night, and now I'm unable to log in Shmi Shmi, even after trying all kinds of nonsense (resetting every part of my network path, my PC, reinstalling the game -- even sleeping 8 hours).  Some part of their system (the lobby server?) believes I'm still logged in.

Sqeenix created a thread for this issue, then shut off their forums.  Apparently there were over 7,000 replies to the thread before the forums went down.  I'm expecting to play an alt for the rest of the weekend.  Yay stress test -- it worked! (I mean that seriously - I'm super glad this issue was found before launch).  :)

EDIT: as of 10:15 am pacific Sunday, the thread is open for posting again.  It's super duper slow, and grew by 100 posts between my post and the thread refreshing!  Yikes.

I also have the same error. 

I also tried to create an alt, but it wouldn't let me do that either.

I wonder if this is "one of those major issues" that will cause them to wipe the servers before Headstart?   That would be horrendous - but they always stated it would be a possibility if something major happened.

This error seems to happen from the login server. Fortunately, NA/EU uses a different login server from JP, so if you get 3102'd, you probably won't be able to play on the NA servers, but you can hop over to the JP servers to play there until then.

And yeah, really really glad they found this beforehand. Let's hope they get all these ironed out before EA.

I've had both the 90k and 3012 error on Excalibur. Zero issues on Behemoth. Both are NA servers which makes it even more odd.

Squeenix has some work ahead of them.

It seems that the 3102 threads keep growing and growing. The Square Enix forums have over 9000+ replies now, and that is just on one thread. LOL. I click on the last page of the forum thread and 6 new pages are added before I get to the end.

I've not been able to get back on since I logged last night. My error however is the "world is full error"

Fortunately, not a huge deal for me. I'm planning to reroll at head start. Not being short (I rolled Hyur not Lalafell) is messing me up.

Hex and I got crit for 3102 sometime around 10:40PM (PST) last night.

Still not fixed 15 hours later - Doh! Hope they manage a fix by next weekend.

Oh wells. I'm happy I at least got some game time in on our world.

It was great seeing random Echoes running around Excalibur, having fun! ^_^

Boo 3102 error. This has not only locked out around 10% of beta players, but also compounds the server full situation. While you are affected by the 3102 error the server thinks you (and everyone else affected) are still logged in.  Which then makes it seem like servers are full when they actually are not. Fixing this error will also ease the server full issue at the same time, is my guess.

Chris and I are going to JP onry level our arcanists instead.  If you cannot make a toon on NA due to the 3102 error, you should be able to make one on JP.

Yep, same here. 3102 since last night.  Looks like SE is aware of it, but:

"The Beta Test errors 3102 and 90000 are still under investigation and unfortunately we have no new information regarding them at this time."

Sigh.  

» Edited on: 2013-08-18 14:58:16

Noooooooooo... all my buddies are 3102 or 90000ing.

I haven't been hit by it (yet). Hope SE can figure out what is going on and fix it before early access.

I was wondering where everyone was last night.  I logged on about midnight PDT and RC was empty, only a couple folks in FC list and mostly unresponsive until others logged on later in the morning.  I guess some of those were "ghosts" of stuck characters.

I hope they manage to get these problems worked out before Early Start and tbh, I hope that they don't shut down tonight without having these errors resolved and tested.  They usually shut down on time no matter what's happening... I've seen them extend a Beta for more testing by a day, only once.

It might be worth trying your hand at a login now, for those that were affected.

25min ago SE updated their twitter page to say they resolved the issue for some players (assuming you managed to get your name added to this thread).

I tried 20min ago and my NA characters still weren't fixed, but maybe some other Echoes will find better luck!

I'm going to keep trying until the end of beta, in the hopes of moving my characters to an inn!

I did add my name to the thread earlier today (around page 500), but I'm still locked out.  BTW, that thread is over 2100 pages now.  Given 10 posts per page, that's 21,000+ players affected by the 3102 bug.  Wowsers!

Emergency maintenance being performed after their previous zero-downtime fixes didn't squash the bug. Hopefully they come back up in time for us to give it one more whirl of testing so we know it's squashed before early access and launch.

I got back in after the fix, played for an hour or so then got a 90000 error and cuold not get back in as lobby maintenance was underway. Might get back on later, here's hoping!

I did get back in after the late night reset, and played until the servers went down at 8am.  (Not surprisingly, I'm a zombie now!)  But the good news is that we didn't see any more connectivity errors after the reset.  Fingers crossed they have the NA/EU data center issues fixed!

Doh! I finally gave up trying to make a character on Excaliber Server. I even set my alarm clock for 1:30am Pacific time but the server was still blanked out. I guess SE wanted people to make characters on other servers. I set a Marauder up on Siren and played almost 2 hours before I got the 3102 error while zoning in the City. Just not my lucky weekend, I guess.

Hopefully I can join you folks when the game opens for early access.

All the Best to you all.

Aww Tildi, well if it's any consolation Excalibur never opened up for character creation again anyway. I was up at 6am PST and tried several times between then and 8am but no joy. There are a lot of us who didn't get on Excalibur this weekend so you are not alone, fingers crossed for next weekend.

They closed all NA and EU servers to new characters @ midnight PDT Saturday, then opened a new NA and a new EU server and directed all new characters to those servers.  Its just a guess, but the way they worded the announcement sounded like they had no plans of opening them again for the duration of the Beta and afaik, they did not re-open them.  I'd have to check their Twitter feed to see if they announced any re-openings.

FYI folks, next weekend is not a Beta, its the "Early Start" of Launch and folks will be required to have a pre-order key.  If you plan on purchasing FFXIV and playing, then I strongly suggest making plans to create your characters ASAP, as soon as the servers are open.  If you cannot, then (contrary to my other comments on the matter) you may want to find a friend who can help you out.

Oh, small catch:  Unlike other games, where if you have an existing character you are not blocked from making alts if they lock the server to new players... when they close a server to new character creations, that is literal.  So make sure the first character that you make (or have made) is the character that you want to "main", because when they close the server, you won't be able to create any more until they open up again.

The position of the leaders of Echoes has not changed on this since day one. 

We urged, pleaded and implored that players make a concerted effort to create a toon, to avoid potential disappointment. 

What we were very wrong about was that we thought it may be an issue specific to legacy servers.  We were wrong on that.  FFXIV just got swamped!

Fortunately, from here on in you have to have purchased the game to play it, which should slightly reduce demand. 

The other things to note were that in phase 4 there was no afk disconnect mechanism in place, so server load was not "real" as many players simply did not log off the entire weekend. Also, the 3102 error kept those players logged in who had been booted, further compounding the issues. The queues got overloaded, and everything melted from there on in!

However, it is still vital that if you were super unlucky in beta 4, and could not get onto the server, that you try right at the beginning of headstart.

Obviously, you don't have to, cos I am not the boss of the internets....or of you....  But it would make a lot of sense if you wish to play in Echoes.

We look forward to seeing you then.  If anyone needs clarification or help, feel free to forum pm me.

*To those who did not get in, I really feel for you, and send you queue hugs, and ask that you hang in there and try again. I was only locked out for 23 hours, but the wait was interminable, it must have been awful to not get in at all.*

I got in, created a character, even played to level 16 or so.  Then I ran into another player with almost my exact same name.  Didn't play that character for the rest of the beta weekend.  The Lalafell rhyming naming scheme tends to make that a little bit more likely I guess, but still bothers me.  Think she may be retired until a name change option comes to the game.  

I'll try again with head start to get back onto excaliber. 

I find that happens a lot when using common name generators or using game lore-based naming conventions.

Yoshi P has confirmed that both the 3012 and 90000 errors have been tracked down and fixed.  He also apologized, and assured us our characters are unaffected by these errors.  http://forum.square-enix.com/ARR-Test/threads/110037

Also from Twitter:

No Character Wipe!

"As we've announced previously, there will be no wipe of the Beta phase 4 data. That data will carry over to early access/launch."

/happymoogledance!