Error 3001

[Iain240]

So after waiting hours I got down to being number 1 in the queue and then i got hit with this bullshit message.

The world is currently full. Please wait until an opening is available and try again.
Now everytime i try to login this is all i get.

Someone explain this crap please? The world is always full and we just get put into a queue but now I cant even make it that bloody far.

[Odstarva]

Everyone in my FC is also having this issue. Also in Phoenix server.

The irony is, we never had this error before (3001). It's funny that the issue they set out to fix only shows up now after maintenance lol

So, I guess they did fix the queue... Because now there is no queue!

[Krotoan]

From their latest response and with possible solutions

■ Disconnects by Error 3001 right before logging in

I’d also like to provide the details and countermeasures regarding Error 3001.

・ Error 3001 Cause #1

A login cap is in place on every World in order to prevent them from going down due to high loads. Despite this, a number of extremely overloaded servers have allowed players to log in beyond this cap, resulting in the allowed number of lobby server connections to fail and cause Error 3001 and disconnect players in the queue.

・ Resolution for Cause #1

We currently have a general idea of what is causing this issue with extremely overloaded Worlds, and a fix is underway. However, these are areas where complex processing is carried out and careful fixing is required for this process. As such, fixing/confirming/implementation into the lobby server will require time. This will be implemented in the maintenance scheduled for December 8, and we are putting our full effort into it, but haven’t been able to determine the full details. Further details regarding this will be announced at a later timing as well.

・ Error 3001 Cause #2

This is an issue that is occurring only on the Tonberry World on the Elemental data center. The Tonberry World has the largest number of login requests of all the game Worlds, and players are helping to mitigate this issue by using the World Visit System and logging into other Worlds. However, due to the way chat connections work when using the World Visit System, we cannot completely cut off a player’s connection with their character’s Home World, causing the total number of active connections to become enormous, and we have confirmed that as a result, a situation similar to Cause #1 above can occur.

・ Resolution for Cause #2

Although we are aware of the relative risk of the Tonberry World going down, we’ve increased the number of network connections to its absolute maximum. Your patience would be greatly appreciated as we monitor the situation based on this tentative fix for the time being.

So right now the answer is, they have a general idea of what is wrong and are working on fixes.

[Shadream]

It seems to be a problem with the Phoenix server. I tried login in on my alts on Zodiark and Odin, both times I was put in a queue. But on Phoenix, I keep getting messages about either full server or error 3001.

Edit: Finally got in queue.

[Iain240]

Right now no. Ive been stuck at 894 for the past 30mins

[Shadream]

Right now no. Ive been stuck at 894 for the past 30mins

The same here. Entered as 858, and half an hour later, still nr 858 in the queue - so not much movement here.

[Iain240]

Ive finally gotten back in queue.. Luckily it was less then 1000. Now to just hope it doesnt happen again.

[Odstarva]

Is your queue number going down though? I get the feeling we're about to experience all going number 1 again and getting this brand new 3001 error!

[Sunako]

I am at 1377 and queue is not moving anywhere either.

[Odstarva]

656 here, and I'm in the same position.

I suppose it is an upgrade to not having a queue at all, but it'd be nice if it was actually letting people in...!
Honestly, I'd feel better just knowing they are aware Phoenix is having these issues and are working on them.

Oh well! I suppose it's the perfect excuse to go outside and get some air