Looking for a solution to this DR1 problem...

[sonicintuition]

I'm using MySQL Servers & Clients version 4.0.23 - same version I've been using for quite a while with no problems. Is there another version of the MySQL system that works with 0.6.1? If so I'd be willing to switch. Let me know, thanks.

Regards,
SI

[cavedude]

That version works with 0.6.1 DR1, or it should rather. I'm using 4.0.21 myself but they are close enough. Since my binaries can connect to the db fine, it's probably pretty safe to rule out the code at being at fault so the problem is configuration... Double check db.ini and make sure the db is correct and also that the user and host both have access to the db named. Try setting the username as root in the ini. If it connects, then you know you have an authorization problem. I know you said you updated the db but just make sure you run through all the updates. If I remember correctly, it was a pair of .sql files, some single queries, and a couple of perl scripts.

[sonicintuition]

Perl scripts? I saw those ..but wasn't sure what to do with them. I tried to run them through the command line via >perl script.pl however I just got a bunch of errors. I put them in the server directory in hopes they would help somehow ..but no. I'll go ahead and revert to MySQL 4.0.21 and see if that makes any difference, and also try root access through db.ini. I'll let you know if it works.

PS - I remember a problem like this with DR3 - sometimes it would work fine, other times I would get this. Then I'd revert back to DR2 and everything was fine. Go figure.

Regards,
SI

[cavedude]

The syntax of the scripts was something like perl script.pl -d dbname -u user -p pass -h host. They have a couple of dependencies for MySQL support which you can grab from ppm the same way you got IO::Scalar if you don't already have them. The item update sql needed to be run before the perl scripts. If you get an error for every item, then your db is not up to date.

Some more ideas popped in my head... make sure db.ini has no white space, and try to stop then re-start the MySQL service. I remember that fixed me up a long while back.

[Sarepean]

For some odd reason, I had a problem like that when I tried 6.0DR3. =/ I immediately copied over Loginserver.ini and db.ini and that seemed to fix my problem (these were from what I assume was my 6.0DR2 install).

Try copying the db.ini from another working install to your 6.1DR1 directory and see if that helps any.