Concrete proof finally provided that the 2002 error has NOTHING is server side issue

Quote:

---

Originally Posted by MiaShino

How are you getting Kansas?
https://i.ibb.co/MC8M640/huh.png



I like the valve employee approach!
//int32_t minutes = {15};
//Why did we code this? This is terrible, never do this.

---

well, thats good, suppose cannot always trust whois lol.

thank you, clears up a couple things. wonder why it showed that though in the lookup... maybe didnt like me looking from Canada? who knows. thank you for the correction

What they really need to do is enhance the launcher/login process to auto-rejoin the queue automatically if any 2002 shows up. If you get d/c'd, that spot should be saved longer as well. Among other QoL things that probably wouldn't take more than a day to add in the system.

Like who thought it was going to be acceptable to throw the error while you say 2k deep into a 4k queue and somehow didn't come back in-time to manually put your OTP back in and then lose your place. Awful design.

Quote:

---

Originally Posted by technole

What they really need to do is enhance the launcher/login process to auto-rejoin the queue automatically if any 2002 shows up. If you get d/c'd, that spot should be saved longer as well. Among other QoL things that probably wouldn't take more than a day to add in the system.

Like who thought it was going to be acceptable to throw the error while you say 2k deep into a 4k queue and somehow didn't come back in-time to manually put your OTP back in and then lose your place. Awful design.

---

The same corporation that authorized setting up one single datacenter to service multiple countries both in the Americas and the EU then thought, this will end well.

Meanwhile nearly every other publisher including EA has the common sense to understand that a minimum of three geographical regions should be covered for NA. Western (Cali), Central (Texas), Eastern (Chicago). I try not to get sassy with these posts but some things just boggle the mind.

Quote:

---

Originally Posted by technole

What they really need to do is enhance the launcher/login process to auto-rejoin the queue automatically if any 2002 shows up. If you get d/c'd, that spot should be saved longer as well. Among other QoL things that probably wouldn't take more than a day to add in the system.

Like who thought it was going to be acceptable to throw the error while you say 2k deep into a 4k queue and somehow didn't come back in-time to manually put your OTP back in and then lose your place. Awful design.

---

what seems odd is that it obviously requires a condition to cause the 2002. what is the condition it requires? the process does work or no one would be able to log in period, so some factor is obviously causing the disconnect in the first place, and only happens sometimes, or no one would be able to play...period.

software either works or it doesnt, it doesnt decide "oh I dont like you, goodbye" there is a condition being met somewhere that is prompting some people to get repeated 2002 errors while other never or hardly see them. I have been in 3700 person queues, dont babysit and get in fine after my wait. others on here may get mostly through then hit, or get in only 10 or 15 deep before it happens.

there seems to be little reason behind what causes it, but it does not seem completely random if you believe the same people are having the issue consistently.

Quote:

---

Originally Posted by MiaShino

The same corporation that authorized setting up one single datacenter to service multiple countries both in the Americas and the EU then thought, this will end well.

Meanwhile nearly every other publisher including EA has the common sense to understand that a minimum of three geographical regions should be covered for NA. Western (Cali), Central (Texas), Eastern (Chicago). I try not to get sassy with these posts but some things just boggle the mind.

---

back in the day with dialup you would have a point. these days... not so much.

Quote:

---

Originally Posted by Puremallace

Someone on reddit was nice enough to do a full technical analysis of the cause of the 2002 error...

---

So, first of all, thanks for sharing this, it's really interesting and its good to see someone posting something of actual value rather than just complaining.

It is actually pretty astonishing to me that the server would drop the connection every 15 minutes and force a new connection. I'd seen a few people claim they were getting 2002'd every 15 minutes and I was pretty skeptical because it didn't seem there would be any reason for the server to drop people from queue in 15 minute increments. But, this data does seem to indicate that's the case, not that it's dropping them from queue intentionally necessarily, but it is introducing the chance for it to happen for no apparent reason.

I do think you're oversimplifying a bit with some of what you say here. 2002 doesn't have nothing to do with the user's internet connection. If there is a problem with the user's internet connection, they will certainly see this error. But, it's definitely also fair to say that probably most of the errors that people are seeing don't have anything to do with their internet connection. I get these errors every time I have to sit in a queue, and I've always been on a wired connection. It also begs the question of why everyone experiences these 2002 disconnects but almost everyone has no problem maintaining a connection to the game once they're logged in if the problem is bad internet. Why can I hold one connection for many hours without issue, but can't with another connection?

Quote:

---

Originally Posted by Puremallace

It has NOTHING to do with COVID as it an issue that goes back 7 years. It is how they choose to handle traffic to their servers and how this client is built.

---

The chip shortage is the reason we're seeing this issue as badly as we are right now. Since the issue is something that appears in 15 minute iterations while in queue, if you're in queue for less than 15 minutes, you'll never see it, even though the issue exists. If you're in queue for 15-29 minutes, you'll still probably not see it all that often, since it's not a 100% chance you'll lose the connection. But if you're in queue for hours and hours you're going to start seeing it a lot.

Previously, they could get by without fixing the login queue code, but that time is behind us. Not fixing this is going to cost them. They can buy themselves time by extending subscriptions, which I can't believe they still haven't announced anything beyond the original 7 days.

If a small interruption in a connection is all it takes to be kicked out of queue, the coding is bad. The client doesn't need to close. It should just keep retrying until it gets back in.

Quote:

---

Originally Posted by Seraphor

If you can solve the issue with a vpn... doesn't that confirm it's an issue with packet loss on the user end?

---

Based on the data provided, I'd say part of the problem does exist on the user's end, in the game client that the user has no control over. It should be trying to reconnect, not simply give up and exit itself.

Quote:

---

Originally Posted by Belisaire

0 and have seen ups and downs but haven't seen Yoshi-P straight up misdirect like this. I'm also concerned that Square-Enix's angle seems to be to just pray the issue goes away.

---

I don't think that Yoshi-P is lying, I think he believes what he has said. It's doubtful that he has a technical understanding of what is happening with the login queue and he is going by information that he has been from the people who do (or are supposed to, as the case may be).

As time goes on, I begin to also have a concern that they aren't addressing the issue with the login queue code.

We'll see what happens... As I've said elsewhere, it is what it is. My advice to everyone is the same as what I'll do myself - if the next time your subscription renewal is about to happen, you feel like you aren't getting your money's worth, cancel your sub and wait until you hear the situation is improved.

Quote:

---

Originally Posted by Kes13a

the process does work or no one would be able to log in period

---

This is false, getting error 2002 doesn't prevent u from playing the game. It prevents u from logging into the game server IF u are not quick enough to just rejoin the queue.

Quote:

---

Originally Posted by Kes13a

or no one would be able to play...period.

---

Incorrect for the same reason above.

Quote:

---

Originally Posted by Kes13a

software either works or it doesnt

---

Again incorrect, software is not an ON/OFF switch, it can work and still have multiple bugs/issues. Please stop making assumptions based on ur own experience when u clearly got no idea.

Quote:

---

Originally Posted by Kes13a

back in the day with dialup you would have a point. these days... not so much.

---

Huh? It is incredibly common for nodes across the Comcast i-bone to become oversaturated. This is.. basic networking stuffs here even for someone like me. It is even more important in modern era than dial up era to properly distribute data centers across large countries due to number of internet users constantly rising.

NTT nodes have been oversaturated for years resulting in still ongoing problems (90006). There is reason why most organizations have region based datacenters and this has been common practice for decades. When I self hosted I owned four virtual servers for good reason, spread out across the country.

Quote:

---

Originally Posted by Kes13a

what seems odd is that it obviously requires a condition to cause the 2002. what is the condition it requires?

---

Yoshi P himself;
"In order to prevent a major login server outage, FFXIV has a limit of "no more than 17,000 total players waiting to log in per logical data center". This cap is set uniformly regardless of how many Worlds exist in a logical data center.

・ The Issue

If the total number of players waiting in the logical data center exceeds 17,000, Error 2002 will be displayed and you will not be able to queue for login."

Quote:

---

Originally Posted by MiaShino

The same corporation that authorized setting up one single datacenter to service multiple countries both in the Americas and the EU then thought, this will end well.

Meanwhile nearly every other publisher including EA has the common sense to understand that a minimum of three geographical regions should be covered for NA. Western (Cali), Central (Texas), Eastern (Chicago). I try not to get sassy with these posts but some things just boggle the mind.

---

It's not much an issue, EU used to actually be in the same data center as NA back when they were in Montreal with their previous provider before they went to Frankfurt.

Would help latency, but it's not so much about traffic as NTT has the infrastructure being a Tier 1 provider, they had been mostly fault-free since SE relocated to their Sacramento facility, it was said it takes 20 racks to run just one world. So having 500+ in one data center allows flexibility, saves on costs. If they use say the NTT Dallas, Texas hub, then if there was any problems routing to Sacramento, every player in those worlds would feel the faults. They would have to substantially outgrow the data center to consider the additional cost of a new location.

Quote:

---

Originally Posted by Kotisimus

This is false, getting error 2002 doesn't prevent u from playing the game. It prevents u from logging into the game server IF u are not quick enough to just rejoin the queue.

---

yes, but if it did not work AT ALL, then everyone would get 2002 and no one could log in. there are those that do not get this error. therefore, it is conditional. point out how that is "false"

Quote:

---

Originally Posted by Kotisimus

Incorrect for the same reason above.

---

please feel free to post the entire part where I said, once in, the 2002 error would prevent you from playing?

Quote:

---

Originally Posted by Kotisimus

Again incorrect, software is not an ON/OFF switch, it can work and still have multiple bugs/issues. Please stop making assumptions based on ur own experience when u clearly got no idea.

---

did you even read and understand what I said?

I said, there is some condition being met that prompts the 2002 error. if software runs into a certain condition, it will error. not everyone is seeing this error. so a condition is being met which drops the connection. this does not happen for everyone. it is possible, can the software work with a bug, it certainly can, but the programmers have a running joke about bugs and errors being caused by "unintended application" which means the user is doing something outside the regular recommended workflow. in this case, something in the connection is causing an unintended response.

no need to be antagonistic, I am in no way saying its not a code issue, there are issues with their code no doubt. just pointing out that it seems consistent for some, but not all. which leads me to suspect its more than just bad code. good to know your first forum post was so benign. I get it, you are frustrated, a lot of people are.