[Microsoft][ODBC Driver Manager] Data Source name not found and no device driver specified


  • I get the above error message when running my VB6 sp4 application on a new Win7 workstation (32 bit machine). The app runs fine on a WIn xp sp3 workstation. The app does require a DSN setup in the ODBC section and I setup the SQL connection the same as I do on an XP machine. I also test the connection on the WIN & machine and it "test successfully". After the error above the app returns a runtime error -2147467259 (80004005). I am attaching my connection string:
    Connection string being used by ADO Data Control (part of VB6):
    Provider=MSDASQL.1;Extended Properties="DRIVER=SQL Server;SERVER=CLAIMSSERVER;UID=;APP=Visual Basic;WSID=CLAIMSSERVER;DATABASE=LRAWITS;Trusted_Connection=Yes"
    Any help would be appreciated.

    Thursday, November 11, 2010 4:57 PM

All replies

  • This article has a lot of help for 80004005 errors.

    It lists the following 5 possibilities as common reasons for your error message:

    1. You referenced your connection incorrectly (e.g. spelled the DSN name, or one of the DSN-less string components wrong); 2. You referenced a DSN that doesn't exist; 3. The user connecting to the DSN or DSN-less connection doesn't have access to the information stored in the registry (see KB #306345); 4. 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); 5. 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).


    Thursday, November 11, 2010 6:06 PM
  • Thanks for the reply. I tried all the suggestions in these articles but still have the same error. Did something change drastically from win xp to win 7 that would cause this behavior? My problems is I can't purchase new pc's with xp but my most critical app won't run in win 7.
    Thursday, November 11, 2010 10:14 PM
  • I don't know what is going on, but Windows 7 (and Vista) have the Data Execution Prevention settings, which may be protecting you too much.  See:


    Thursday, November 11, 2010 10:46 PM