Errors on loading EQ2World.exe

[ichijin]

I have gone through the forums, and updated my port to 9102, and nuked the DB before that so it would have the 'proper one' as the error I am getting was for an incompatible DB with the server version. I am using the latest SVN, and just redownloaded the DB into it from 9102. Still getting the errors for opcodes, armor, weapons, etc. And once server gets through all that to where you should be able to connect it says: eq2emulator.net:9102 not the login server. Any help with these is appreciated.

[Bion]

ichijin change your port back to 9101 and redownload that db then change it back to 9102 to update it. I dont think 9102 has all of the database in it just the difference from the other one.

[ichijin]

Thanks tryin that now.

[ichijin]

Nope, that didnt do it either. AFter it redownloaded the DB on 9101 it spammed all the errors, and I changed to 9102 and ran it after that and it still spams the errors.

[Bion]

I am not sure as to why you would be having problems. is the user you set up in the world_db.ini have premissions to access your database?
here is a clean database just been updated as a test called eq2test
http://www.box.net/shared/pi5r3xnpt8
it loads up fine. tested with 175 svn
you can source it using heidisql or with the command line for mysql

Code: Select all

mysql -u username -ppassword database_name < eq2testclean.sql

[ichijin]

That one did the trick. Thanks a bunch. Not sure why the downloaded one isnt working for me.

[John Adams]

Good job, Bion. I was going to do the same, but you beat me to it =) Btw, if you use this DB (SVN 175 binaries) you need to set your LoginServer update port to 9102, and use the latest binary EQ2World.exe from SVN.
If you are using Sourceforge release binaries for 0.6 (dated Jun 22 2008), you must set your LoginServer.ini update port to 9101 and source in this database. Same way as Bion posted.
You can also source this 0.6 DB in, set your port to 9102 and run the latest SVN to get all the DB updates - but this is where you may run into the problem I have reported to LE about the update server timeouts (not 'exceeds', but actual data delivery timeouts). So best use Bions DB as a base.