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

    Question

  • trying to install sql server2005 on a windows 2003 server box.

    getting msg below at the sql server .  i looked at other posts on trying to uninstall  SQL Native Access Client and norton antivirus.  i could never find the snac on the add - remove programs and this server does not have a virus protection program yet.

    here's the history of the installs on the server:

    wanted to test a 2005 upgrade so:

      1) installed sql server 2000 then sp4 then restored some databases to it - all OK

      2) tried to upgrade to sql 2005 but ran into problems and left it at that.

    had a disk drive crash on the d drive so lost the installs but not the operating system

    when the drive was replaced, left alone for a while

    then wanted to test a straight 2005 install

      1) removed the broken 2005 attempt

      2) removed the 2000

      3) installed 2005 and got the error on the subject line:

    TITLE: Microsoft SQL Server 2005 Setup
    ------------------------------

    SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

    i've gone through as many of the forums that i can and have tried several things - like uninstalling 2005 and installing pieces and parts but but nothing seems to work. 

    Thanks!

    Dan <><

    Thursday, October 19, 2006 3:41 PM

Answers

  • It sounds like the SNAC version you have might be corrupt or incompatible.

    Go to Add or Remove Programs and find the listing for "Microsoft SQL Native Client". Remove this component. 

    Then try the install again.

    Michelle

    Friday, October 20, 2006 12:30 AM
  • Actually that was a good work around as downloading a newer version would have forced the install to run again where as in the previous case it was failing quickly becuase it thought it was laready installed.

    Glad you got you machine back.

     

    Michelle

    Monday, October 23, 2006 4:57 PM

All replies

  • It sounds like the SNAC version you have might be corrupt or incompatible.

    Go to Add or Remove Programs and find the listing for "Microsoft SQL Native Client". Remove this component. 

    Then try the install again.

    Michelle

    Friday, October 20, 2006 12:30 AM
  • Thank you so much for replying.  last attempt was to install just the sql server commonent - no others like analysis services or integration services. 

    i looked at the add / remove programs both before, during and after the sql server database services failed attempt and the add/remove has never shown a program called MS sql native access client (SNAC). 

    when i start the install, the installing prerequisites window shows the two components that will be installed: snac and the sql server 2005 setup support files.  the snac goes to a green arrow almost immediately while the 2005 setup files takes a few seconds.  i dont know if that helps or not.

    the add remove programs just has:

    • microsoft .net framwork 2.0
    • microsoft office 2003 web components
    • microsoft sql server 2005 backward compatibility
    • microsoft sql server setup support files (English)
    • microsoft sql server VSS writer
    • msxml 6.0 parser
    • windows server 2003 service pac 1

    there is oracle express installed on this machine and it uses odbc to link to sql databases on other boxes.  we use it as a gateway from unix oracle to windows sql server.

    thanks again!

    Dan <><

     

    Friday, October 20, 2006 1:45 PM
  • It definatel looks like the problems is the "Microsoft SQL Server Native Client" layer.  At this point your machine thinks that it is already installed but the install is broken.

    Follow the directions in the following article to clean up the machine and then try again.

    http://support.microsoft.com/kb/909967

     

    Michelle

    Friday, October 20, 2006 4:36 PM
  • uninstall manually - did the following (shows issues with some of the directions)

    • it said to delete the local security groups.  but i never could figure out how to do.  the article it mensions didnt (at least to me) show how to delete.  so i just went on
    • looked and stopped one sql service
    • made sure sql server support files were installed
    • attempted to run the arpwrapper.exe but got the error - registry enumeration failed.
    • so went to the if you have problems section (that's where you go if you get the registry enumeration error)
    • went through the guids listed in the registry under unistall.  there was never one for snac. but did run the start command for each sql server one i found.
    • checked back on add/remove and there were no sql programs listed as installed.
    • it then says to remove the snac in add/remove - but it's not there - that is the problem.

    when you start the sql server 2005 install and it says it's installed the snac and the setup files, if i stop right there, i should see it in add/remove programs, is that correct? 

    i see the setup files installed but have not see the snac.

    any other ideas?  do i need to reload the c drive with a new copy of the operating system and try again?

    thanks!

    Dan <><

    Friday, October 20, 2006 6:29 PM
  • i went out to the website and downloaded the .msi file for snac.  it was slightly different from the .msi that came on the DVD (3511k vs 3516k). 

    the dvd version when i clicked on the msi file just returned me back to windows explorer. 

    the snac from microsoft's website executed and finally installed the snac.

    the install worked perfectly after that.

    thanks for your help

     

    Monday, October 23, 2006 2:27 PM
  • Actually that was a good work around as downloading a newer version would have forced the install to run again where as in the previous case it was failing quickly becuase it thought it was laready installed.

    Glad you got you machine back.

     

    Michelle

    Monday, October 23, 2006 4:57 PM
  • Hi,

    I've been handling SQL Server upgrades for many years. The most dangerous path for an upgrade is to directly upgrade 2000 to 2005 (or 7.0 to 2000). That's because you create the risk of destroying the databases on the existing server and causing data loss.

    The best approach embraces the fact that we typically upgrade a windows server when the mfg warranty on the hardware has expired. So, you have a new box and windows server. If you don't, the store the backups on another resource (disk, tape, flash drive, etc...) and copy from or restore from that resource. Rebuild the Windows server or uninstall SQL Server 2000. (I would have fresh windows to insure the best chance of success.)

    Install SQL 2005 & configure on the new W03 SP1 server. migrate the users. (this worked easily with 2K but MS has hosed that functionality in 2005 from what I can see; you must use a script they provided that is flaky. You will need to manually create the users it fails to migrate.) Backup the dbs on 2K, shut down 2K on the old machine and restore the dbs to 2005. associate the users with the logins.

    Now you have a fullly upgraded database server and your databases are unhosed. This may not be elegant but it guarantees the MS upgrade process won't destroy your databases or bring down your business for days.

    If you have a completely hosed system, then rebuild the system (and the drives) and follow the steps above to a successful conclusion.

    z.

    Wednesday, November 01, 2006 11:21 PM
  • For anyone interested I had the same issue but with a failed installation rather than an upgrade.

    It was the Sql Native client, and while the sqlncli.dll was in the \Windows\System32 directory there was no entry on the drivers tab of the Data Sources (ODBC) utility (control panel\administrative tools\Data Sources).
    So I uninstalled SQL Native Client in the Add\Remove programs. The dlls however (unfortunately) remained, so I deleted them, then reinstalled the SQL Native Client component separately, and checked that it showed in the Data Sources \ Drivers tab. Also tested a connection to another Sql 2005 machine.

    Then I re-ran the full SQL Express installation and it worked.

    I think perhaps there were registry entries that were not correctly intialised while those files remained.

    Hope that proves useful to someone.
    • Proposed as answer by Harry Elzinga Thursday, December 25, 2008 9:21 PM
    Tuesday, October 16, 2007 3:55 AM
  • Hi all,

    Had the same problem whith installing a new instance of SQL Server 2005, besides the default SQL Server 2000 version. The solution Simon Francesco described worked as described. Thanks for your contribution.

    Harry
    Thursday, December 25, 2008 9:23 PM
  • Hi Simon,

    thank you the post. It really works. I was struggling to re-install SQL 2005 due to this annoying error.
    I followed your step and it worked.
    I thank you for this support.
    Tuesday, November 03, 2009 7:41 AM
  • Dan:

    This problem drove me crazy for weeks. What finally solved it was to inspect the Windows\system32 directory for the sqlcni.dll. I had previously installed Microsoft Visual Web Developer 2009 and as part of its install, it had put on Sql Server 2008 perhaps as part of Sql Server express. the upshot was that the native client was not installing correctly for 2005.

    I uninstalled Sql Native Client, then went to Windows\system32 and removed the Sqlncli.dll and Sqlncli.rll. I left sqlncli10.dll figuring it was from Web developer. I then ran regsvr32.exe sqldmo.dll from the command line. Next I ran the
    Native client install wizzard from the SQL Server installation CD.

    I then reinstalled Slq Server 2005. I noted that it did not try to install native client, which it had been doing for the last month. The installation stalled for a bit, but then concluded and I was able to run Sql Server 2005 and create a database.

    This was on a dell standalone machine running XP pro. I had previously upgraded windows installer to the latest version.

    Hope this helps all the other quitely pulling their hair out. 

    John


    Wednesday, November 04, 2009 6:37 PM
  • I know this is an older post, but I had to comment on this.  A client of ours server had gone down and a replacement server was brought up in it’s place.  Windows Server 2003 was installed on the replacement server and a restore was done.  Unfortunatly the client didn’t have a current backup of the system state, so a lot of the software (including Microsoft SQL Server Express 2005) had to be re-installed.  We also were running into the problem re-installing SQL express 2005 and finally came upon this thread.  After uninstalling all SQL related software, including the native client, we removed any remaining  SLQ*.* files from the system32 directory.  SQL Server express 2005 installed flawlessly after that.  Thank you so much Simon!

    Friday, September 24, 2010 1:56 AM
  • @Dan

    Thank god... I've struggled one day with this problem. I've done a lot of sql server installations but never had this kind of problem...

    For all our german speaking friends seeking this error in german:

    Fehler: [Microsoft][ODBC Driver Manager] Der Datenquellenname wurde nicht gefunden, und es wurde kein Standardtreiber angegeben.

    KR

    Friday, November 12, 2010 9:21 PM
  • I ran into the same problem with a console app that was connecting to a system DSN. It was deployed to Windows Server 2008 Standard SP2 64 bit machine. I kept getting this error message every time I ran it:

     

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

     

    After a few attempts at the solutions in this post, I went to visual studio and looked at the project properties. I noticed that platform target under the build tab was set to x86. I changed it to Any CPU, I rebuilt the project and like magic...it worked!

     

    Hope this helps

    Thursday, August 11, 2011 1:18 PM
  • I ran into the same problem with a console app that was connecting to a system DSN. It was deployed to Windows Server 2008 Standard SP2 64 bit machine. I kept getting this error message every time I ran it:

     

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

     

    After a few attempts at the solutions in this post, I went to visual studio and looked at the project properties. I noticed that platform target under the build tab was set to x86. I changed it to Any CPU, I rebuilt the project and like magic...it worked!

     

    Hope this helps

    i have this same issue also but its happen when i want to configure at ODBC.. need help on this :(

     

    tq 

    Tuesday, September 27, 2011 6:24 AM