List:MySQL ODBC« Previous MessageNext Message »
From:Gary Wong Date:August 20 1999 3:56am
Subject:Problems with NT/Oreilly Website/ASP/MySQL/MyODBC
View as plain text  
Hi, I am having problems with the following setup:

- NT 4.0 SP5/Latest MDAC
- Oreilly Website 2.3.15
- ASP 1.0b
- MySQL 3.21.29a-gamma (running as service - I used mysqld-nt --install)
- MyODBC 2.20.24 for NT
  The DSN is set up to use Host= "." (Named Pipe)
  Options Checked: "Return matching rows", "Use manager cursors (exp)"

I have an ASP page that accesses a local MySQL database.  As soon as
the page is hit and the query is ran, Website dies with this in the 
server.log:

> closesocket() failed, code = 10038
> accept() failed, code = 10004. This probably means the TCP service has failed.
> Attempting recovery...
> closesocket() failed, code = 10038
> accept() failed, code = 10004. This probably means the TCP service has failed.
> Attempting recovery...
> closesocket() failed, code = 10038

Website crashes, but MySQL dosen't - it just continues on.

Here are some interesting findings:

1)  If, in the DSN, I used Host= "localhost" instead (TCP connect 
    instead of Named pipes), I still get the error messages in the 
    server.log and the page stops loading.  However, Website dosen't 
    crash!  Then, if I try to run the same ASP page again, it works!
    Any ideas?  I don't trust it!

2)  On a different NT computer, I can use MyODBC to connect to
    MySQL and it works fine.

Thanks for any insight!

Gary Wong

Thread
Problems with NT/Oreilly Website/ASP/MySQL/MyODBCGary Wong20 Aug
  • Re: Problems with NT/Oreilly Website/ASP/MySQL/MyODBCPeter Carter20 Aug