Data source name not found and no default driver specified

Help!!
I can connect fine to my Db from my test server at home but when I move it to my server (my web server and SQL server are on the same machine) I get the following error:

Microsoft OLE DB Provider for Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Can someone please lend a hand. Thanks!

How are you connecting to the DB on the production server? DSN, DSN-less? If DSN, is the DSN setup correctly on the live server? If DSN-less, is the driver present? Does the live DB server have the same name, db??

it's connecting to a server DNS.

fix:

Delete the USER data source name and define it as a SYSTEM data source name.

In Windows 2000:
-> Start -> Settings -> Control Panel -> Administrative Tools ->
Data Sources (ODBC):
- User DSN : delete the specified User DSN
- System DSN : create a new System DSN

Hi there.

What's the fix when using a non-DSN connection?

Thanks in advance,
another Newbie

Sounds like you have a bad connection string - show us what you've got and we should be able to help you.
Alternatively, this resource should be able to get you going: http://www.carlprothman.net/Default.aspx?tabid=81

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

I had this error and want to let you know how it was resolved.

First, this was an ASP web application using a vb 6.0 dll to get data from a sql server 2005 database on a 64 bit windows server 2008 enterprise (vista like) server. I could only get the dll to work in component services as opposed to simply registering it.

It all worked fine upon setup, but after four windows updates one night, the error above was posted in the event viewer, and the web app crashed.

Here is the resolution:

In a 64 bit windows server operating system, there are TWO odbc managers. When you pull up the usual menu for the odbc / dsn system, it is for the 64 bit odbc manager, and 32 bit applications (vb 6.0) will not work using these dsn's.

This is where the 32 bit odbc manager is:

C:\Windows\SysWOW64\odbcad32.exe

I hope you do not have to go through what I and three Microsoft Support engineers had to to figure this out.

Jonathan

Hi,

What exactly you did to solve this problem? I am facing the same problem on Windows Server 2008 64-bit and SQL Server 2008.

Reply #7 from Jonathan worked for me ... thx Jonathan!

There are 2 versions of ODBC to worry about on 64-bit machines: the 32-bit version and the 64-bit version. So you have to Add or Change in 2 places to cover both types. Start - Admin Tools - Data Sources gets you to the 64-bit version; Start - Run -
C:\Windows\SysWOW64\odbcad32.exe gets you to the 32-bit version. Do all your adds/deletes/changes in both.

This same problem happened to me with VS2005 and a third party ODBC database. Essentially the same symptoms. I could preview data, but when I tried to run the app, it failed to access the data. The reason is that Vs2005 is a 32 bit app, but my app was being compiled as a 64bit app. So they used different ODBC managers and DSN's. When I changed the target CPU in the compile options to x86 (32bit), voila, problem gone!

My application is in asp.net 2.0 and connect with sql server 2005. my connection string is DSN=DsnName;Uid=sa;Pwd=pwd;

my development server is 32bit windows 2000 and my production server is 64bit windows 2008. my application running fine in development server but when execute it in production server, I got the following error.

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

To solve this I have done following two things is production server,
1) execute
C:\Windows\SysWOW64\odbcad32.exe
create a dsn as "DsnName" in System Dsn.

2) execute
C:\Windows\SysWOW64\odbcad32.exe
create a dsn as "DsnName" in System Dsn.

Now when execute the application in production server Im getting the following error :
ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired


Can anyone help me ??

Check this link EMBEDDING SQL IN C#.NET for details on how to connect to SQL server database from C#.NET database applications as well as Java database applications. It also describes how to pass embedded SQL queries, calling stored procedures, pass parameter etc.

Shahriar Nour Khondokar Shahriar Nour Khondokar[/URL]

Hi there!I'm new here.Good to be here.Want to talk about much more information regarding programming and development.Would like to learn about jake? That I have come to find out is almost a link between Cakephp and Joomla? How does these really merge and supply an impact to web development in php??

Jeff,
Great Call! I had a similar situation where the vendor did not support 64 bit ODBC drivers. I compiled to x86, and it used my 32-bit driver.