September 5th, 2003, 10:32 AM
Data source name not found and no default driver specified
We had a web site that works in windows NT very good with a DB in Access. Our clients migrate to Win 2000 and now the connection to the DB doesn't work,...the error is this:
Error: Access is Denied.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
/directory/progs/utils.inc, line 17
The code is this
Connect_String = "DSN=lmsfamilia;"
What could it be?
September 5th, 2003, 10:49 AM
Make sure your client has a DSN named lmsfamilia on his machine.
To check that, simply go to :
Start-->Programs-->Administrative Tools-->Data Source(ODBC)
then click the System DSN tab and *look* if its there...
If not, then create it!
Hope this helps!
September 5th, 2003, 10:56 AM
I've already done that DSN
I'm sure the DSN is created in Data Source(ODBC)
I'm really confused...two days with this error....the DSN is created...the users IWAM_ and IUSR_ have the rigth permision to the folder....so ...mh?
September 5th, 2003, 11:16 AM
OK then there is NOTHING *I* can do from here...in Montreal!
You'll need to DEBUG
Start from the beginning,
Create a simple .asp page that does this:
then move up one leve...
Create a *second* .asp page that *tries* to connect to your database.
Use an OLEDB connection instead of a DSN to connect to your Access database
Look here: http://www.able-consulting.com/ADO_Conn.htm
Now you do NOT have much choice to go step by step in order to identify the problem
I wish I could help you more...honestly!
If the OLEDB approach doesn't work then try creating a *NEW* DSN following the steps in the wizard.
Hope this helps!
September 5th, 2003, 12:16 PM
Double-check your DSN. If you have a typo in the path to the .mdb file you can get this error.
If the .mdb file is in some location outside of your web, make sure the IIS user account has permissions to the .mdb file.
You can download and install newer MDAC packages from MS at www.microsoft.com/data You need to download Jet (Access) drivers separately.
It is remotely possible there is a registry permissions problem where IIS can't get to the DSN registry entries.
September 6th, 2003, 07:50 AM
Try removing "DSN=" from the connection string... we've often found that that is the cause of problems even though it shouldn't be....eg
(Plus remove the SemiColon)
Connect_String = "lmsfamilia"
Also.. make absolutely sure it's a system DSN
December 28th, 2010, 12:06 PM
Thanks, I had mistakenly created a "User DSN".
Definately make sure it's a "System DSN" when troublshooting this issue.
June 13th, 2011, 04:39 PM
I re-factored my file to put spaces between all the '=' symbols for readability. Unfortunately I did a global search and replace. That inadvertently added spaces between the DSN and the name. i.e "DSN = sourceName". Well some of you probably know that there can't be spaces between DSN and the name. So make sure yours looks like this: "DSN=sourceName" Hope this helps someone!
June 14th, 2011, 12:16 AM
Thanks for the reply. Did you happen to notice this topic is 8 years old? I doubt the original poster is reading.
Originally Posted by vcoleman
It is a truism of American politics that no man who can win an election deserves to. --Trevanian, from the novel Shibumi