1017 Clarification

First off please do not turn this into a bitch-fest, I am hoping to get some actual information.

What exactly is the 1017? Is it an issue where the FFXIV server is full or does it have something to do with the log-on server?

Currently I feel that it more has to do with too many people trying to log on at once in the same server, which would mean it is a log-on issue not a server issue. I also feel this because occasionally I will get in a que for my server (Excalibur) then get kicked out with a 1017 error.

I do not know how all of the tech works so any clarification as to what exactly the error means would be greatly appreciated.

Also, I apologize for any grammar or spelling mistakes.

It's not a bug or issue at all. It's a deliberate change they made to server logins. In an extreme knee jerk reaction to high player populations, they first started locking character creation. But that quickly applied to nearly every server. And it wasn't good enough. They next replaced the login que with a hard population cap. Anyone trying to log in while the server was at it's maximum just gets an error. That's the 1017 error.

The devs did this deliberately. Locking out countless players, just to provide good gameplay to those few who are lucky enough to get in.

But it didn't end there. Their third knee jerk response was to halt sales. You cannot buy a digital copy of the game until further notice.

When the server is full, you get a queue
When that queue gets full as well (yeah... seems possible...) you get the error

Ahhh, okay, that makes sense. Thank you both for the info, I had thought that it was an actual issue they were still working on fixing. I knew they were capping the population, but it had been bothering me why the que's were not working either. Thanks again, and good luck getting in until they fix the issues.

Quote:

---

Originally Posted by Hysterior

When the server is full, you get a queue
When that queue gets full as well (yeah... seems possible...) you get the error

---

Not completely true, I was #35 in queue for a minute or two supposedly, and then got kicked with the 1017

So successful (or hyped I should say) it begins to implode on itself.

Quote:

---

Originally Posted by Hysterior

When the server is full, you get a queue
When that queue gets full as well (yeah... seems possible...) you get the error

---

Sadly not always in that order.

Today I got the queue (#49), then while I was waiting happily in my queue, I got 1017 out of nowhere.

Fun times.