Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. READ MORE

Connector connect error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Connector connect error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Last Update:

Apr 14, 2023 10:13:04 AM

Updated By:

Sonja_Bauernfeind

Created date:

Nov 14, 2017 6:15:09 AM

A data connection fails with:

Connector connect error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

 


 

Resolution:

There are three likely reasons for this issue to occur. Neither of the issues are Qlik related, but depends on ODBC setup in Windows. 

  • The database drivers used in the DSN needs to be updated
  • Referred Data Source Name (DSN) name is not available for the user/server
  • Database driver used in DSN is damaged or not available

 

Validate that DSN is available to the reloading user/server.

  1. Open the document using QlikView Desktop client
  2. Go to Script Editor (Ctrl+E). If reload issue occurs with server, skip to step 12.
  3. Open ODBC editor based on the driver being 32- or 64-bit
    • Tools > ODBC Adminsitrator 32 bit..
    • Tools > ODBC Adminsitrator 64 bit..
  4. Validate that the used Data Source Name (DSN) is on the correct tab
    • User DSN - These DSNs will be available for the currently logged in Windows user, i.e. the user running QlikView desktop
    • System DSN - These DSNs will be available for all users on the machine, i.e. both the devleoper user and any QlikView service user
  5. Add DSN to System DSN if required to be used by multiple users

Validate that DSN works in Windows

  1. Select the DSN that fails in QlikView
  2. Click on Configure...
  3. Click on Finish
  4. Click on Test Data Source...
  5. Validate that the connection works
    • Success - The connection now also works in QlikView
    • Failed - The DSN settings are incorrect. Contact database administrator for details.
  6. Close the ODBC administrator and reload the QlikView document
  7. If issue occurs while QlikView Server is reloading the document, obtain the Data Source name from the Scrip editor > Data > Database > ODBC > Select or from the connection string itself. (i.e "ODBC CONNECT TO <System DSN name>)
  8. Make sure to create the same Data Source using Windows "ODBC Data Source Administrator" on the specific QlikView server reloading the document.

 

Cause:

The Qlik Engine cannot find a corresponding or the correct ODBC driver. Typically not an error in the Qlik product, but an issue with the environment configuration. Qlik is unable to find the correct ODBC driver or an incorrect one is configured. 

 

Environment:

Qlik Sense Enterprise on Windows 

Labels (1)
Contributors
Version history
Last update:
‎2023-04-14 10:13 AM
Updated by: