Its been nearly a week now with no action done about this by Square Enix yet and I'm starting to lose patience. Time to add to the cluster of posts about this.
Error Code: (30002)1346862993,0,5
Details: Server transfer error during ANY instanced content.
Unable to log in (for almost a week now) after the server crashed handling the instance of the Garuda battle I was doing. On the log in screen it says my character is in "The Howling Eye" zone but trying to log in just times out and gives me that error code stated above. I'm certain this is a server issue that requires Square Enix action.
Steps:
1. Do the hard Primal Garuda battle.
2. Win/Lose to exit the instance.
3. See if the game goes into an infinite loading screen, then the server has messed up transfer and now you are stuck there forever.
Date & Time: 8pm ~ 11pm September 4th
Frequency: Receive error every time I try to log on since date above.
Character Name: Xeonerable Fenrir
FFXIV Server: Balmung
PC Manufacturer & Model Number: Custom Built
OS: Windows 7 64-bit Professional
Graphics Card: Nvidia Geforce 9800 GTX+
ISP: Brighthouse Networks
Type of Internet Connection: Cable
Area/Zone: The Howling Eye
What you were doing in the zone: Primal Garuda battle (hard mode)
Were you in a party? (how many members if yes): Full party, 8 Members
How many characters were near you when the error occurred?: Full party, 8 members
Can you log back into the game at all?: No
Others affected by this problem:
(Character Name / Server)
- Xeonerable Fenrir - Balmung
- Edeon Vails - Balmung
- The Crow - Balmung
- Pietro Nobelhart - Balmung
- Foxichi Hexoff - Balmung
- Snow Reinheart - Balmung
- Pritz Titan - Balmung
I have talked with Square Enix customer support via chat about this issue already. Yet still nothing is happening so I'm posting to help give this problem some urgency..
UPDATE
I just got home today and tried to log on the game and it finally loaded up! It loaded me into an empty Garuda arena and then booted me back out to Coerthas a few seconds later. Anyone with the same problem as me should try to log on.