Forum Moderators: open

Message Too Old, No Replies

mySQL 4.1 - W2003

difficulty connecting

         

txbakers

4:32 pm on Aug 8, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I'm having difficulty connecting to the mySQL 4.1 server on my W2003 server.

I've installed the myODBC Connector as usual (works in 2000) but in 2003 it's not connecting - throwing an error, something about upgrading to a newer mySQL client (which 4.1 is the current latest production I believe).

All the code is the same from 2000 to 2003.

Is there a setting in IIS 03 I need to worry about? Can't find it. ASP, etc. are enabled.

Funny thing though, I can connect with a .NET connector for my .NET (aspx) pages. It's just regular ASP through ADODB

THANKS

dataguy

9:57 pm on Aug 10, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Do you have the latest version of MyODBC installed? (v. 3.51.11) There was a problem with using earlier versions (3.51.9 and before) with Server 2003 which was only rectified earlier this year. I don't know what the extent of the problem was, but I know I couldn't connect from a 2003 server until I had the newer version of MyODBC.

txbakers

10:39 pm on Aug 10, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



let me try....thanks for the suggestion

txbakers

11:03 pm on Aug 10, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



that did the trick, but now I'm getting an error. Has the connection string changed with the new release?

Here is the error:

[MySQL][ODBC 3.51 Driver]Access denied for user 'ODBC'@'localhost' (using password: NO)

And here is my usual connection string (been using it for years without incident):

var STRINGSQL ="Driver={MySQL ODBC 3.51 Driver};server=localhost;Database=charms;Option=1,user=#*$!x password=#*$!xxxxxx";

thanks.

defanjos

11:59 pm on Aug 10, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Try this:

var STRINGSQL ="Driver={MySQL};server=localhost;Database=charms;Option=1,user=#*$!x password=#*$!#*$!#*$!";

I believe I had that problem before, and removing the 3.51 part fixed it.

txbakers

12:24 am on Aug 11, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



nope. The earlier version of the ODBC connector didn't require it, but the 3.51 did.

Removing it didn't work.