Log in

View Full Version : Zone not available

xilo
10-03-2004, 05:16 AM
I just updated to 5.9-DR2 and now whenever I try to login a character, I keep getting the "This zone is not available" error. How can I fix this?

Yes, I DID search the forums. Yes, I DID read the other posts. None of that helped. I had 5.8 working last night with no problems.
jimbox114
10-03-2004, 05:24 AM
I had this problem to a extent. The first time I woudl try to log in I would get that. However if I tried over and over, usually within 2 or 3 trys it would log me in.

Not sure what caused it, probably cause my server pc was slow.
Malignus Wingnut
10-03-2004, 05:42 AM
When you hit enter world on a character, if the zone is not already loaded into one of your unused zone.exes, it will proceed to load the zone for you. Sometimes your client is faster than your zone.exe (this is especially the case if you are trying to play from the computer that is hosting) and this causes you to get the Zone is not Available message. Just give the zone.exe 5-10 extra seconds to load the zone and then hit enter world and your problem should be resolved.
xilo
10-03-2004, 05:51 AM
Nope, that doesn't do anything. What I do is load world.exe and then load a 1 zone version of Boot5Zones.bat and wait for everything to load. Then I login. It was working last night when I had 5.8, and now that I updated to 5.9-DR2, it's doing this crap. Here's the error I'm getting from eqemudebug.log

2004/10/03 17:48:51 GMT: Zone 7995 crashed. Errorcode: 1/6. Current zone loaded:gfaydark. Current clients:0. Caused by:
Malignus Wingnut
10-03-2004, 05:56 AM
5.9 DR 2 is by all means a developer release and therefore is bound to have bugs of one sort or another. I use 5.9 dr1 so i am unfamiliar with this error.
xilo
10-03-2004, 05:57 AM
Works on other people's servers. Bleh, I shouldn't have updated EQ -.-
Derision
10-03-2004, 06:14 AM
I just updated to 5.9-DR2 and now whenever I try to login a character, I keep getting the "This zone is not available" error.

I upgraded to 5.9DR2 this morning and had that same problem. In my case, zone was complaining about a missing column in the altadv_vars table. I sourced in EQEmuCVS/SQL-Files/altadv_vars.sql and that recreated the table with the missing columns and all was well.