Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
ajithsachin
Partner - Contributor II
Partner - Contributor II

ODBC Is Not Connecting From Scheduler

Hi All,

     From management console if i am scheduling my qvw it is showing the odbc connection failed.

     but the same application if i am reloading manualy there is no error.

     i have changed the qlikview services login to administrator then also result is same.

     Can anybody help..

Regards,

Ajith

4 Replies
Shoes
Contributor II
Contributor II

Hi, i have the same problem.... and i cant find solution , did You find??? please help 🙂

martinpohl
Partner - Master
Partner - Master

did you set your ODBC connection as a user-DSN ? So it is only visible to your user. You have to set it as System-DSN.

The other thing is the way of authentication. Is there a user and password set or windows authentication? In a reload job, the service user is starting the reload, so he needs access to data.

Regards

Shoes
Contributor II
Contributor II

I have system-dns , all credentials in. Funny storyy that the same user - Amin can reload the same script in client QV, but Distribution Service runned on Admin too cannot connect via connector and ODBC, so ports are open, antivir off and still the same error :

2022-03-09 13:27:58.1111259 Information 2022-03-09 13:27:58: 0062 ODBC CONNECT64*
2022-03-09 13:27:58.1111259 Information 2022-03-09 13:27:58: Error: Failed to connect to QlikView Connector.
2022-03-09 13:27:58.1111259 Information 2022-03-09 13:27:58: General Script Error
2022-03-09 13:27:58.1111259 Information 2022-03-09 13:27:58: Execution Failed
2022-03-09 13:27:58.1111259 Information 2022-03-09 13:27:58: Execution finished.

 

Shoes
Contributor II
Contributor II

Problem solved, i just copy->paste->replace qvconnector64.exe from client folder to distributionServ folder and it works. It means that error was in exe file... very very strange...