Error 9000 to 3102 to 1017 to "Unable to load JP server list"

Seriously?

Get an error 9000 last night as im porting, then i get 3102 for the next hour. Finally decide to give up and goto sleep. Get home from work this afternoon only to find im getting 1017 error repeatedly (wtf happened to the queue system?) and now i cant even load my character/the JP server list?

Can we fix this shit now please?

Homehopper
Tonberry

My client is at "Unable to load JP server list" too atm.

Mine randomly switches from Unable to load JP to unable to load NA/EU. And I keep getting 90000'd. And 1017'd. And 10102'd. This has been my ONE night off for the next two weeks and my connection has been as bad as it was through early access. Such a waste, and so incredibly frustrating. And I realize that it is a Saturday morning...but why are the servers full at 6 in the morning!?

Quote:

---

Originally Posted by RickiFake02

Mine randomly switches from Unable to load JP to unable to load NA/EU. And I keep getting 90000'd. And 1017'd. And 10102'd. This has been my ONE night off for the next two weeks and my connection has been as bad as it was through early access. Such a waste, and so incredibly frustrating. And I realize that it is a Saturday morning...but why are the servers full at 6 in the morning!?

---

In Japan it is night time and peak hour. I don't know what's up with the NA/EU ones though.

Finally got in after spamming the log in over and over and over. 15 minutes later i got error 90000 for no reason... All i was doing was fighting a mob, wasnt even porting.

To put this in perspective ive had 0 errors throughout the whole BETA period (p2, p3 and p4) and 0 errors through early access. What the hell happened?

Gday, I experienced a disconnection from error 90000 at about 1:30pm GMT +10 and now it is going on 9:00pm GMT +10 and I have tried off and on quite a few times and have yet to actually login again.

I have experienced the exact same errors from 1017 to unable to update the Jp server list to error 2002. How disappointing to not be able to play on the weekend when you have time off from work :(

Bump, cause i got nothing else to do while the game ive invested more money in than i should of refuses to work.

Quote:

---

In a lengthy forum post, producer and director Naoki Yoshida (aka Yoshi-P) outlined what steps have been taken to stabilize FFXIV's game world. Yoshida noted that all Final Fantasy XIV servers now have login restrictions to prevent a flood of logs and re-logs from causing them to crash. Login restrictions are most likely to be implemented during peak times, which Yoshida says are between 9:00 p.m. and midnight. Each server can support a theoretical maximum of 5,000 concurrent players.

---

Ironic that the same man that fixed the game the first time is also the one to totally break it the second time. This is supposedly the cause of error 1017, this is outrageous, remove the log in restriction.

Removing the log in measures will just break the servers. They just need to fix the que system to actually work more then one in 10000000000000000000000000000.

Servers on JP were down early this morning around 3:30am GMT for me, got kicked out of a guild quest.
Attempted to login a few times, but the game kept kicking me out of the character selections screen saying "server full" lol. So then I checked NicoNico Live and saw other Japanese players had similar issues logging in, but not all.

Decided to go sleep.

Apparently the issue was fixed, but now I can't load JP list. SO I don't know what the so called "fixed" part of that was.
I'll keep trying tho.

It's weird cause first EU servers were having so many problems now it's JP servers.
I guess square really didn't prepare well enough for this many players.

There is now a queue that you enter so no more spamming num 0. It got me back in and seems to have fixed the log-in issues.

Well its the EU/NA list that is now not loading :P

After 10:00pm GMT +10 and am again attempting to login and was getting 1017 and now I am getting "Unable to update the group JP character list" repeatedly. This now makes it about 9 hours that I have been unable to login. Love the game and can't wait to login, but I do have to say that I am very unhappy with the service I am not receiving. :(

Quote:

---

Originally Posted by Rethiness

There is now a queue that you enter so no more spamming num 0. It got me back in and seems to have fixed the log-in issues.

---

How do I enter this magical que, I just get the 1017 error before it crashes my game completely.

This is soooo frustrating >.<

Ever since I got disconnected like since 5 hours ago, I couldn't get back anymore -.-

The queue has been there. The problem is that the queue can also fill up. Think of it this way: you're waiting in line to get into a nice classy bar (the game). The bar is full (1017). The bar is so classy, no one wants to leave, so they start sleeping there (Afk login). There's two sections of the bar; one for cool people (JA), one for rad people (NA/EU). The two sections each have their own entrance off the sidewalk, and you can queue up for either door (server lists). If you do get in, there's different rooms on each side (worlds). The sidewalk is full (no queue accessible). So many people are trying to fit onto the sidewalk, that someone stumbles and falls over, knocking over everyone around them because they're packed so tight (server list down). Sometimes, inside this classy bar, someone gets squished because of how many people are inside, and they black out (90000). Sometimes the bar is so packed that the bouncers can't get to them with a glass of water and a swift kick out the door (3102). However, they're in the process of building new rooms for this super classy bar (new servers! yes, really!), while people stuck outside, either on the sidewalk, or across the block just staring at the sidewalk from afar (forums, people awaiting physical copies).

The Producer announced in his very long and polite recent letter that based on monitoring server usage throughout the beta, they knew on August 25th that server capacity was insufficient, and immediately began procuring additional hardware. He then detailed the process of literally building a new game world - as in, the machine. They have bought the hardware, they have installed the software, and now they are in the process of testing them. Let me ask you this - If suddenly there were 50 servers in JA, 50 in NA and 50 in EU, but all the new ones were buggy and crashy and laggy and started erasing people's characters... don't you think that would be worse?

I can't get into the game myself right now due to a shipping issue - and I'm pretty pissed that I don't even have the same problems you all do. But I looked into what I could do about it, and I'm weighing my options (I might just buy a physical copy locally and tell Amazon to shove it).

As for what happened between early betas and now? Perhaps, not enough stress testing, and a failure to gauge consumer interest properly. At least not enough time between the real stress test that was EA and the actual launch.

What is really annoying me about this whole 1017 fiasco is that on occasion, you get a "loading" screen with a background of one of the cities....sits there for 15-20 seconds making you "think" you've been successful in getting logged in only to get the confounded 1017 error. I'm using a PS3 and I wish I could just tape the "X" button down while I waited instead of button mashing that button. I only get to play FFXIV on the weekends!

Edit: 15 minutes after posting this, I finally got a queue notice and got in. Not planning to log out at all until this evening (only going AFK to run to the nearby (within a mile) food place to get food to go....hopefully I can play all day!

10:50pm GMT +10 and finally logged into the queue and luckily was not disconnected before loading into the world. So basically I was forced offline by error 90000 for over 9 hours and now I can play for a short while before heading off to sleep, woohoo. Thanks for letting me in SE.

I do wish you could have prepared a better server/network infrastructure before, seeing as these problems existed in Phase beta 4 and there was a week of downtime between early access. You created a fun game but did manage this aspect poorly. I am pleased to look forward to when these problems will be a thing of the past. Thanks Square Enix for your time. :)

I keep thinking when I log back in im going to find a lot of ppl just AFK standing there... we should just log of when we are done for the night, let other people in.

Quote:

---

Originally Posted by awakingemotion

Ever since I got disconnected like since 5 hours ago, I couldn't get back anymore -.-

---

Same issue for me.

Is the IT doing the work?
Seriously ?

350k copies sold / log in/ whatever, you can't cope with it, how are we looking at million copies sold and etc?
Really, SE an international firm, has such failure, I am sad for you...Quite unbelievable this is happening to SE ...

Not even 1 hour of playing and I get disconnected after an instanced quest with error 90000 when I begin to zone out of it.....

Would like to add me to the list here.

Just be patient, they're doing maintenance. You guys complain about bugs and then you complain when they're putting the servers down to fix them.

I didn't even read this thread.... but...

They're doing what they need to do to get things running smoothly. They're trying their best to keep the game online and as stable as possible in the meantime. That's why there's a heavy world restriction.

It takes time to order parts, put them together, prepare the software, update the infrastructure code, then put the hardware in place and merge the systems together. If they actually got it done in under 2 weeks after release, I'd be very impressed. They're not going to update you guys every step of the way... Especially since the last thing they need to do is confuse people. They've said they're working on it, so they are. They're not just gonna up and walk away from a game they put this much time and effort into. Just be patient and stop crying. Otherwise find another world to play on that isn't as populated.

Keep in mind, each world is comprised of what would be more than likely a full rack of servers... In order to accommodate for 5000 people constantly connecting to them, they need to add more to each and every world, which is 25 per datacenter. You're talking adding multiple servers to 50 different worlds... That's a ton of work, and I think that's really what people fail to see here. A video game doesn't just create itself overnight... Nor does the infrastructure it runs on - the part people misunderstand the most.

Right now they're doing lobby server maintenance. Thats why you may end up getting kicked out, but the worlds are left online so you at least have a chance of getting back in.

90k, to 3102, to 1017 is the cycle you're just going to go through every time.

90k = General Disconnect from Servers

3102= Character still logged in and hasn't disconnected yet (seems to be about 10mins)

1017 = world full.

Keep in mind, 90k could be something on your own network too... Routers, switches, ethernet cables, the port on your computer, software running on your computer... etc

The system is obviously broken. For those saying the queue system is still there, you are right, HOWEVER its not that the queue is full. After the last 90k error i tried to get in again only to hit the 1017 wall for another hour, suddenly it just decided to FINALLY put me in queue... "Number in queue: 7" soooo unless the queue limit is like 10 people i highly doubt that is the issue. Regardless i managed to snag about 2 hours of gameplay before i got 90k error again at which point i just gave up and went to sleep.

Trying to log in now, a solid 12 hours or so since i last tried... "Unable to update JP group character list" - BROKEN!

Just as i was getting used to spamming log in over and over and over again for hours on end just to get ingame, they go and pull a fast one. Now, i cant even get to that point, getting "Unable to update JP group character list" for the last 2 hours... lol?

[edit] Its Tuesday guys, Tuesday. If you servers cant handle the load on your average run of the mill weeknight, we have some serious issues.

*Casts Error-code 3 Death on 9000, 3102 and 1017*