Ehm, question.

[Issac]

We are well into patch 2.1. ARR successfully launched months ago. There has been plenty of time to patch in queue systems. In fact, I remember seeing a queue at one point.

So why am I seeing 1017 right now? Where's my queue? Oh, I don't get one?

FFS SE...

[Razzle]

I got some friends who are still getting spammed with 90k... Looks like it affects specific group of people... Could be by location on the globe or by certain ISP... And to the people who are going to say "Itz ur interwebsz!11" Its not - FFXIV is the only game my friends are having errors on.

Anyway sorry to hear you're having problems OP and hope you get it fixed. (as for me, I'm clean error-wise thankfully)

[Issac]

I got some friends who are still getting spammed with 90k... Looks like it affects specific group of people... Could be by location on the globe or by certain ISP... And to the people who are going to say "Itz ur interwebsz!11" Its not - FFXIV is the only game my friends are having errors on.

Anyway sorry to hear you're having problems OP and hope you get it fixed. (as for me, I'm clean error-wise thankfully)

Thanks for that. Fortunately I'm already in.

But 1017 is the error given when the server is full and when the server doesn't want to give you a queue yet as to not over-burden the lobby server. It's complete BS and I can't believe it's still around.

[Johnist]

1017 is nothing to do with the server being full. It means your character is still logged in due to a disconnect and you can't log back in until the server logs your character out. They can't create a queue for that because you're not queuing, you're just waiting for the game to boot your character.

No, that's 3012, not 1017. 1017 means Server is Full. Queues are for when many players are trying to log in at the same time as there is open room for them on the server.

[Alberel]

No, that's 3012, not 1017. 1017 means Server is Full. Queues are for when many players are trying to log in at the same time as there is open room for them on the server.

You're right... not sure why I thought that. Having said that I wasn't aware anyone still got the 1017 error. The few times I've seen or heard of it since last year were actually bugs that required you to cancel and try again. It was actually nothing to do with the server load. I play on Phoenix which was the highest populated server by SE's stats released a few months back yet I haven't seen any login queues (or need for them) since 2.1. The only way what the OP describes could be down to genuine server load is if a very large population of the server got disconnected at once and attempted to log back in yet by all accounts those experiencing the 90k errors are in a very small minority.

[Naunet]

Dangit, I can't find that incredible gif of Bahamut destroying swaths of Eorzea with error messages. The best thing to come of all that nonsense. xD

[DannyNobuser]

To be honest I get a similar queue every once in awhile I just cancel then retry and I get in every time it does not fail. But to answer your question you would have to ask a dev they are the only ones with access to the coding and can explain why this happens

[Enkidoh]

I'm wondering if it's only affecting certain servers too - some servers are more populated than others. Having said that, the only time I get 'server is full' errors now is usually between 5pm-10pm my time on a weekend, in other words, peak time for my server, when most players are able to play, being a weekend and all. Usually I can get on after cancelling and trying again.

[Johnist]

/sigh... OF course the 90k/1017 issues exist on those LARGER POPULATION SERVERS... They will continue to exist as long as you try to log in on a server with a huge population during prime-time hours.