Qlik Community

Qlik Sense Data Connectivity

Discussion board where members can learn more about Qlik Sense Data Connectivity.

Highlighted
aschmeelk
New Contributor III

DSN not found on task reload

Hi folks,

Running Qlik Sense April 2018 release; I have created a 64 bit DSN on our Qlik Central node Server and when I'm in the Data Load Editor of my App, the connection works fine.  It's when I create a Task to reload the App that I get the following  Error: Connector connect error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

I have verified ownership, the DSN, basically everything I can think of, why would the Reload Task fail in QMC when the App loads without errors from it's Data Load Editor? 

Completely stumped here!

Labels (3)
1 Solution

Accepted Solutions
prashanthi_gn
New Contributor III

Re: DSN not found on task reload

Also make sure the driver is configured in all the nodes.
8 Replies
jwjackso
Valued Contributor

Re: DSN not found on task reload

Is it a System DSN?

aschmeelk
New Contributor III

Re: DSN not found on task reload

Yes system dsn
prashanthi_gn
New Contributor III

Re: DSN not found on task reload

what kind of driver is that?

If its a Oracle , then can you please check if there is tnsnames.ora file in the networks/adimin folder.

prashanthi_gn
New Contributor III

Re: DSN not found on task reload

Also make sure the driver is configured in all the nodes.
MVP
MVP

Re: DSN not found on task reload

When you ran the reload successfully from Data Manager, were you working with Desktop or were you opening the app from your workspace on the hub?

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
aschmeelk
New Contributor III

Re: DSN not found on task reload

My workspace on the Hub.
aschmeelk
New Contributor III

Re: DSN not found on task reload

No, not Oracle. MySQL driver.

aschmeelk
New Contributor III

Re: DSN not found on task reload

That was it! I had forgotten to create the DSN on our Rim node.  Thank you!