Odd connection issue
 

So I decided to reload my OS last night and all was going smoothly till I starting setting up my minilogin. For some reason the database isn't cooperating with me today. I keep getting kicked back to the login screen when trying to get in the game world. The only errors I can find in my log files are:

[12.20. - 18:35:25] [LAUNCHER__STATUS] Zone dynamic_05 has gone down. Restart timer started.
[12.20. - 18:35:25] [LAUNCHER__STATUS] Zone dynamic_03 has gone down. Restart timer started.
[12.20. - 18:35:25] [LAUNCHER__STATUS] Zone dynamic_04 has gone down. Restart timer started.

[12.20. - 18:35:09] Client 'Skalz' was destroyed before reaching the connected state:
[12.20. - 18:35:09] Client sent initial zone packet, but we never got their player info from the database.

I am guessing the two problems are related but after four reinstalls of mysql and the database I am still getting the same error.
Things I have tried...logged in as an administrator, UAC is off, all firewalls and anti-virus are off, windows defender is off, reinstalled mysql several times using different revisions each time, reconfigured mysql several times, checked my port and ip settings, reloaded the emu map files, updated the .conf files, made sure i was using the correct opcodes.conf for SoD, made sure mysql was recieving connections using Navicat, made sure I didn't miss any updates between database and emulator revisions.

I am using a custom compiled emulator revision 1753 with peqdb rev1751. The custom compliled emulator was previously working. I compiled emulator rev1771 and tried it but I still get the same problem.
I tried mysql revisions 5.5.58, 5.1.53, 5.1.52 and 5.1.51(this one was working yesterday) all were 64 bit. Using perl 5.10.1007 x86 which was also previously working.

Any ideas on where to look next?

Did you compile with the 64-bit MySQL? The DLL files need to match your compile. I've always used 32-bit since that's the only way it compiles for me.

MySQL has nothing to do with compiling binaries....Perl on the other hand does...I have tried Perl x64 and get numerous symbol errors which is why I was using Perl 5.10.1007 x86 at the time both sets of binaries were compiled.

It uses the headers from MySQL, so it would appear to me that there is a dependency.

I reinstalled MySQL 5.1.50 on my computer and this is the same version that was used when I compiled my binaries. Up until yesterday I had been using that version for several months with no problems. Any other ideas?

Found the problem. Apparently Norton Ghost was interfering with the function of mysql.

Guess I didn't figure it out after all....this problem will not go away. Any ideas what might be causing it?

lerxst2112, while I disagreed with what you said I did try it and much to my dismay it did not work.

I have tried every single version of mysql I have ever used and all of them give them same error. I have tried this on two seperate computers using two different operating systems with nothing else installed and it still will not work.

All of the sudden everything I have learned about the emulator setup over the past two years is completely useless.

If you run zone.exe by itself what happens? I'd guess you're missing a DLL file in which case you should get a dialog telling you so. Use dependency walker (http://www.dependencywalker.com/) to figure out what you're missing.

If I had to guess I'd say it's probably zlib since that is easy to overlook, however I don't know if zone uses it or not.

I ran zone.exe by itself and these are the log files it generated.

The main error I see is a failed connection to world which is expected since world.exe was not running. The second error is a plugin error which shouldn't be needed for this to function.

zlib.dll is part perl correct? I set visual studio to include perl, perl/lib/core and my dependancies folder as part of it include, dependancies and etc. for compiling so unless it is excluding sub directories zlib.dll was present at the time I compiled it. I will try it again however.
The dependancies folder I mentioned is the Dev kit 2.0 found here: http://www.georgestools.eqemulator.n...u_DevKit20.zip

I tried recompiling the binaries and I ended up with the same problem. I then started reading other connection issue posts and I read this again http://www.eqemulator.org/forums/showthread.php?t=32753

The first time I read that post I didn't think anything about it but today it hit me that is the same error I encountered on my second computer. I sourced that sql into my database and it seems to have fixed the connection problem......while that is good news I am not gonna draw any definitive conclusions this time I am just going to wait and see if it keeps working over the next few days.

Well, I think the problem may be that you said you had a database issue, but it appears to be connecting to the database fine. From the first log you posted it looked like zone was perhaps not starting at all, hence the troubleshooting step.

If you still want to narrow it down, I would recommend cleaning out the logs directory, running everything, and trying to log in. If you get stuck, dig through the logs, which should just be for that attempt, and see if there are any errors. From there you can troubleshoot those issues.

Error messages may be misleading, but if you keep digging you should be able to find the first error and go from there.

I am certainly going to continue trial and error testing with this problem. I know how to cause this problem but if I can eliminate it at will it would be helpful in knowing that the solution is correct and not just a fluke.

I had been deleting old log files as I went along to prevent myself from accidentally reading an old log file. You are absolutely correct about how error messages can be misleading.

One of the problems with this error was it never produced a bad session/time stamp error on my Vista machine it only generated that error on the XP machine. Another one was unable to insert character data into the database. Both of those errrors were easily bypassed by manual insertion of the needed data. I was thinking the whole time that I had just made an update mistake which may not have been the case.