Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.


Connection error to the server

Hi all

can you know why i am getting the bellow Error

Error :

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




5 Replies

Re: Connection error to the server

Dear Madhu,

The error clearly tells you that the data source name is not found. Make sure that you have created the ODBC connection and tested that connection.


Kaushik Solanki

Valued Contributor II

Re: Connection error to the server


You need to install ODBC driver in your PC. Install it according to your windows version and 32 or 64 bit.

Hope it helps.

Not applicable

Re: Connection error to the server

Hi Madhu,

You will need to create the ODBC connection first.

Also check that the Drivers is installed (you can get the list of installed drivers by going to ODBC Data Source Administrator > Drivers tab).

Re: Connection error to the server

Dear Madhu,

You will have to create an ODBC connection on server.

For which you would need to install the appropriate database drivers.

I would recommend that you contact your IT team and ask them to create one database connection for you.

Look below link for how to create an ODBC connection.

Creating ODBC Connections on Windows | ScreenSteps Workgroup | ScreenSteps Desktop 2.9 and Workgroup...


Kaushik Solanki

Re: Connection error to the server

The disadvantage of ODBC is that you have to define a so-called DSN in the system on every platform where you plan to use this data connection, and using Windows software tools. OLEDB doesn't have this annoying disadvantage because all data connection parameters are defined and passed in the CONNECT statement.

To define an ODBC DSN on the remote machine, you must log in into that machine using Admin privileges, open Start->Administrative tools->Data Sources (ODBC) (this may be different on your remote machine, depending on the Windows release) and start configuring a new System DSN with the exact same name that your CONNECT string expects. Make sure that an ODBC driver for the target database is installed on the remote machine before trying to define an ODBC DSN.