I'm currently trying to run a classic ASP application which I've been given source code for. I want to set up on my 64bit Windows 7 dev machine and am having trouble with an ODBC based data connection to a MySQL instance. I'm seeing the error: Microsoft OLE
DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified /includes/.asp, line 100 What I've tried: The connection is DSN-less. The application is running under IIS app pool with
local system permissions. w3wp.exe can be seen running under NT AUTHORITY/SYSTEM in process monitor. The application is running under IIS app pool with 32 bit applications allowed to run. Have tried with Connector/ODBC 5.1.10 64 bit version only installed
from http://dev.mysql.com (At this point no driver was listed under C:\Windows\SysWOW64\odbcad32.exe but was under C:\Windows\system32\odbcad32.exe) Have tried with Connector/ODBC 5.1.10 32 bit version only installed from http://dev.mysql.com (At this point
no driver was listed under C:\Windows\system32\odbcad32.exe but was under C:\Windows\SysWOW64\odbcad32.exe) Have tried with Connector/ODBC 5.1.10 32 bit and 64 bit versions installed. Verified driver name is not misspelled. Along with other checks from here
http://support.microsoft.com/kb/306345. Driver={MySQL ODBC 5.1 Driver};Server=localhost;Database=DBName;User=root;Password=Password;Option=3 Additional Information: I'm monitoring in process monitor, and the two results are: PATH NOT FOUND (Looking for .asp/web.config
which seems odd. BUFFER OVERFLOW Both entries show: User: NT AUTHORITY\SYSTEM Process: C:\Windows\SysWOW64\inetsrv\w3wp.exe C:\Windows\SysWOW64\odbcint.dll I'm stumped can any one make a suggestion on how I get this running in the context I have described?
Have you checked the most common scenarios for this error listed in
this article:
Quote From Above Article
This usually happens in one of the following scenarios:
you referenced your connection incorrectly (e.g. spelled the DSN name, or one of the DSN-less string components wrong);
you referenced a DSN that doesn't exist;
the user connecting to the DSN or DSN-less connection doesn't have access to the information stored in the registry (see
KB #306345);
you used an English or localized driver detail for your connection string when your system is not set up in that language (see
KB #174655); or,
you are missing the connection string entirely (this can happen if you maintain your connection string in a session variable, and your sessions aren't working; see
Article #2157).
Let me know if this provide a workarround for you.
Thanks.
Marked as answer by Lloydz on Feb 28, 2012 07:07 AM
Cognize80
1 Post
MySQL ODBC Issue: Data source name not found and no default driver specified
Feb 21, 2012 05:50 PM|LINK
odbc asp mysql
Lloydz
2335 Posts
Microsoft
Re: MySQL ODBC Issue: Data source name not found and no default driver specified
Feb 23, 2012 02:03 AM|LINK
Hi,
Have you checked the most common scenarios for this error listed in this article:
Let me know if this provide a workarround for you.
Thanks.