I zoned into the Thicket from Mamook, trying to get Staging Point. I got Failed to Read Data error upon zoning. Now whenever I try to log in, i get this message over and over.
I don't know what to do, anyone else get this message?
I zoned into the Thicket from Mamook, trying to get Staging Point. I got Failed to Read Data error upon zoning. Now whenever I try to log in, i get this message over and over.
I don't know what to do, anyone else get this message?
ive had similar things happen to me, the best thing to do now is have a friend log you in and move you back out from that area and stay away from it til we have a maintenance
Had that problem, turns out some of my .dats became corrupted for the Port Jeuno zone, couldn't repair or replace them with ones my friends sent me, some error about not being able to delete the file. Had to run the Error Check on my C-Drive and after that proceeded to reinstall FFXI and the problem was fixed.
I ran Error Check, and the problem seems to be fixed, at least for now.
Thanks for the replies.
Just a note, this seems to be happening to a lot of folks upon zoning between new TAU zones - something from the unscheduled maint. this week. Two seperate folks had issues just last night with this that I know of, and the only cure seems to be the error check, or at worse reinstalling ;;
My 75 thf friend ran into the *exact* same thing last night, zoning from mamool staging grounds into Mamook I believe...he could login to his mule, but every time he tried his main it gave him that error.
For my other friend, who i know is on ps2, he couldn't get on last night from this issue - and downloading todays patch fixed it.
Sorry for this necro bump.. but the problem still persists.
It seems the only way to fix it is to do a file check. Whenever i zone into the thickets from mamook, or from the staging point, i must run a file check to be able to log back on. I dont even have to repair, i just have to run the checker. after it has run, i can log in and perform all normal functions in the zone. it's really annoying to have to do this any time i want to do a merit pt or an assault...
There has to be someone else that is experiencing this problem...
Have you called a GM within POL? They can't fix a problem they don't know about though, with that said, I'm sure they'll just tell you to re-install the entire game to shut you up.
Honestly, if you have to run the Disk Error Check everytime you zone in, it'd be more beneficial to do a clean reinstall after a Disk Error Check.
I concur, even though its a huge pain, nothing is better than a fresh reinstallOriginally Posted by kyod
Did they fix that bullshit with all of the system files getting deleted with the reinstall?
Supposedly, yes.Originally Posted by Firedrag0nn
This happened to me once as well, zoned into Ve'lu(tab), and game would crash every time I tried to log on. Called a GM from a mule, he tried to move me when I would log on but could not, game would continue to crash. Tried this a few times and eventually he told me to contact tech support when they opened(this was on a fucking saturday too).
I said fuck that and did a full reinstalled and was able to log onto my charc, but could not send tells, or use any chatmode, move, etc. I called another GM from a mule and got Senterpi(who is quite fucking cool). He couldn't move me either but could send me to jail, and is exactly what he did. From there he sent me to my homepoint and everything has be fine since.
I know it doesn't really help you much but it worked for me. Maybe try asking a GM to do this for you.
I had this happen to me once when I zoned into CN for escort like 2 years ago.
Just have someone log in and move you to your HP and it should work.
happened to me, Metalworks would fuck me up. I made my friend login as me, then move me to somewhere else, then i'd login again.
Its happened to me inbetween ru'lude and upper jeuno... just wait like an hour and log back in again if you dont trust anyone with your info.
Thank you for the replies. I'm going to try a reinstall of Aht Urghan to see if that will fix the problem for me. If not, full reinstall it is