I've been afflicted as well. Was about to go mine and boom, error 9k. An hour later, still 3102
Name: Xyno Edajos
World: Coeurl
Printable View
I've been afflicted as well. Was about to go mine and boom, error 9k. An hour later, still 3102
Name: Xyno Edajos
World: Coeurl
Stuck in 3102 myself.. F it, I'm going to bed, do my nightshift and I'll see tomorrow at 6am if I can log on again.
World; Balmung
Character: Nyala Nyaru
already posted but didn't put int he info so w/e. In many mmo's, if your character is logged in while oyu log in it still lets you log in...so why not here? Isn't that kinda basic nowadays?
Yup. Logged out using "Log Out" and now getting 3102 upon trying to log back in.
Well just by trial and error they are going to figure out how to program this damn game. Problem is, it may be another year before everyone can consistently log in.
Also stuck in 3102.
Character: Drake Fury
World: Sargatanas
To those complaining about bad customer service: use your head. With all that's going on, with this many people playing and this many things going wrong, it's obvious that the call and chat services are overloaded.
At least under Tanaka's reign of terror we could log in!
They really need to fire the NA/EU project team leader. Beta is over and Early Access is over it is time to see some reprimand.
All I want to do is play.
The login boss of this game is the most OP and unfair boss in any FF game.
Any version of Omega Weapon has nothing on this beast.
Nicely done! They do a 10 hour maintenance to fix things and now for the first time ever, I'm getting 3102. Seriously, well done.
Rude SE Chat Support
Sorry you were saying?
Just got hit by 3102 as well. :< I'm not as upset because luckily it happened 10 mins after finally beating Garuda....I'm sure I will be in the near future however the more it plagues me.
Same issue. I logged in just fine, then logged off in Gridania and now error 3102...
Thanks for the official update, not that we shouldn't have all known they said they wee watching things closely that they would have caught this. 90k and 3102 are back, but don't forget these are general error codes, and its not the same cause that results in these errors as it was in Open Beta.
90k just means you got disconnected, and hundreds of things can give you 90k, very few will be widespread and anything that is not a widespread problem take a lot of time to find and fix.
3102 is clearly not the one from open beta where you DC while teleporting into a new zone. Now I wish it would have been the same one as they would already know how to fix it as it has been fixed once.
To be honest anyone who expected everything to be perfect after such a large infrastructure change and big update are oblivious to how these things work. Ideally there would have likely been another week of testing this before going live, but the community (so much QQ) and situation (launch of game and way more subs they expected) forced their hands to get it out ASAP, and it seem like they missed something.
Now I am not happy to be 3102 right now, but I am not going to QQ bout it. Maybe I will start to be a bit mad if I see the issue still happening late tonight. FFXIV is a GREAT game with some server issue that need to be ironed out, and as far as I am concerned the game is more then worth the wait, and I have plenty of RL stuff i can do while I wait, for now at least.
Really ! really???
...
For all the people who can log in and play go away get off the forums so that those of us who are having problems can vent and get service.
Was getting 90000, followed by 3102, but I have had this 3102 error now for over 3 hours.
I logged in. Awesome! No 1017 (yet). Okay. Logged out. Went to create a new character (just to see what worlds were locked and were not, a friend was asking). Exited out of that. Went to log back in. 3102 You are still logged in. Are you serious? ....... Sigh.
I swear some people will defend SE even if one of their representatives came over to their house and held their head in the toilet lol.
Well, that's at least one thing SE shares with their customers, then. I gave them the benefit of the doubt until today,Quote:
To be honest anyone who expected everything to be perfect after such a large infrastructure change and big update are oblivious to how these things work.
almost 2 weeks after early access, but the results, up to now, are rather "underwhelming".
Just posting in case they go through and fix characters one by one again.
I got hit with this around 8am and am still 3102'd. Halp!
At least you guys got to log on. I can't even get the server list to load.
I was able to login this morning, I went to grab breakfast, when I came back I was kicked from server with "2002" error... for past 30 minutes i'm stuck with "3102"... very disappointing
I've been plagued by 90000 and 1017 and 3102 since open beta and none of my tickets have been answered by anything but an automated msg. I logged on this morning after the several hour maintenance, got into an instance matched dungeon and hello 90000. Then followed by the infamous 3102. I can't do jack now.
Don't worry guys, u get 7 free days that you can spend on the character log in!! ;P
Logged out to restart my machine. Logged back in and got 3102
and yet again the error went away i could log in 10 mins later dc from server 90000 and now back to 3102....
Still can't log in with this error. What a shock!
3102 also; usually I'm quite patient but now I'm not so sure...
I was locked out of the latter beta phases thanks to errors, had to deal with hour+ login times during release, and now when I logged out I can't get back in thanks to 3102.
If anything, it's taught us once again: "Never log out, ever... Ever"
As an aside; a friend said to try and make a JP character and then log in with that to see if it fixes it. Now it's 3102'd also x_X.
SE; I wouldn't mind these errors so much if you took your time in fixing things and made sure they were done right, but it feels like fixes are being rushed out without being tested properly. D: I Know you're trying to please everyone and it's hard, but take a deep breath and make sure it's done right ><.
I got hit with 3102 also. logged in just fine when the servers went up a lil before 6am. logged out and restarted pc and an hour later still getting 3102.
exited game in the inn at Ul'dah
in SE we trust!
- by a player sitting out because of 3102 error
Was playing for hours just fine, but then crashed. Now I am stuck on 3102 also.
Character: Silly Turtle
World: Goblin
Have submitted a support ticket, so maybe I'll get fixed. Have tried logging into other characters and making new ones on other servers, but no luck.
Hmm...
After maintenance I thought I should spoil myself and buy a new office chair so my ass doesn't become numb while playing FFXIV. Well at least my ass won't get numb from seeing error 3102.
Nice post. Let's see...
1. I don't, but I am hoping SE does have some of those.
2. I know it isn't, but shouldn't be THIS difficult for a top developer.
3. I don't, but I am wondering if SE does for this game. That would explain like... everything!
4. I have no idea. But again, a top developer should..
5. In my job, I do know what I need to know. And I do know how to put in charge. Clearly SE didn't know how to put in charge of the servers management.
So, to sum up. That's why I didn't make an MMORPG, neither I charged for it, neither am I planning to charge monthly for it.
Nice post. Let's see...
1. I don't, but I am hoping SE does have some of those.
2. I know it isn't, but shouldn't be THIS difficult for a top developer.
3. I don't, but I am wondering if SE does for this game. That would explain like... everything!
4. I have no idea. But again, a top developer should..
5. In my job, I do know what I need to know. And I do know how to put in charge. Clearly SE didn't know how to put in charge of the servers management.
So, to sum up. That's why I didn't make an MMORPG, neither I charged for it, neither am I planning to charge monthly for it.
And yeah, of course:
1017 on my japanese character.
3102 on my european character.
CAN'T EVEN CREATE A NEW CHARACTER IN THE BRAND NEWLY OPENED SERVERS ATM.
SE, you screwed up... and people are losing their patience (or at least I am).
I was playing this morning around 7am. Logged out at an inn. Came back on to play and get the 3102 error! I was giving them slack because of the massive popularity but enough is enough! Get this fixed ASAP SQUARE!
I think the funniest thing about this is the people acting like the issues were to be immediately resolved even after prior to this update SE stated there will be issues starting out due to the rush to log in.
Every newly launched MMO has issues, some even far worse to the point the MMO is down for days just to allow people to use a major feature that no one reported bugs on since they treated it as a demo and not a beta. Anyone who says no MMO has launch issues, especially major ones, is delusional - WoW's initial launch took far longer to stabilize than what SE is doing - they stated to expect issues to hopefully persuade people to not immediately rush on. The issues are indeed fixed, notice the lack of 80 topics an hour about 1017? This error is still due to the session not clearing properly but the login issue (the main error people complained about) is indeed fixed.