Error 5006 (trying to connect to Aether Lobby)

Hello,

I see no other posts between now and yesterday regarding any unplanned maintenance or server issues so figured I should post. Also the world status shows as green (online) so was not expecting any issues.

However, I have loaded up the game three times now and each time getting 5006 error cannot connect to lobby. I have also tried Chaos instead of Aether and same issue.

I also noticed, which may be related, that when I went to mog station to enter in my heavensward code it said could not connect to server under my list of characters.

So client-wise, it is all up to date. Connection wise, I am on 100mb/s virgin media fibre optic broadband with no issues to speedtest or other sites. I am trying to connect from Engalnd UK (altho I play on a NA server mainly).

Nevermind, i'm in game now. Must have been a blip.

Actually I just got the same error message logging into the Aether
Data center. And then it lets you in. This is something that SE should
look at.

Hi I go to log into the game and I enter my login and password
and that works fine then I click on Play and then I click on Start like I normally do.
It says "connecting to the data center" and I am getting an error of
"The lobby server has encountered an error 5006"

What is going on with your servers right now.. This is nothing on my
end it is something on your end!

Can some one look at this!

Screenshot has been attached and can be
seen at http://i62.tinypic.com/2yywoy1.png

This happened on May 16 2015 at about
5:00 AM MST I play on the Mateus server.

Can some one please look at this issue?


http://i62.tinypic.com/2yywoy1.png

Hard to say for certain without seeing a hex code that typically gets logged with 5006, but basically it is because a resource was not found or otherwise inaccessible. Could be the file was still locked after patching, or a flaky transfer from the server resulted in a retransmit that delayed delivery longer then expected.

If you haven't rebooted since the last patch you could give that a shot. If you frequently suspend/hibernate your system (rarely actually shutting it completely off), it would be a good idea to get in the habit of doing a full power down periodically. Some updates won't actually complete until the system is restarted. The file system itself can also use a reboot as an opportunity to do some light maintenance as well which can help prevent/resolve some conflicts that may rear their ugly heads after a while.

I got the same this morning (Balmung in Aether cluster), but it let me log in at the second try.