Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have 64 bit of QlikView server installed, however some of our apps uses 32 bit odbc connection and hence requires to run task as external via command like.
Task runs on its time. Document log shows it completed successfully, however QMC status continuously shows task as running.
When I go to WIndows task manager and kill qv.exe then the task shows triangle warning icon, however under task status it shows as task successfully complete.
We are running QV SR1.
What can be done to fix this issue, the issue this creates is that reload engine shows that it is in use and job that falls after that fails due to reload engine not being available.
Hi.
Why don't you just use ODBC CONNECT32 statement ?
My plan is to eventually try that. Since I am new at my work, I don't want to change anything that is being schedule without fully understanding all the consequences.
In Detail this is what happens.
"C:\Program Files (x86)\QlikView\qv.exe" /R "Q:\qvapps\sampleapp.qvw"
This is causing major issues at our end because, you cannot run schedule jobs as it hangs and takes away reload engines from other task.
We are running 11.0 SR1.
Anyone facing similar issues, Any solution.
Any updates and insight. Did anyone face similar issues.
Dear Friend,
Same things happen me also but not every day weekly two times or three times it happeining . in my case every my schedules are running based on windows schedule some times this task hanging particular Qvw file. afterwards once i was killed my qv.exe session. it was completed succesfully. i cant understand y this problem happening. even that time of system memory and CPU utilization also under limit. Please any one suggest any idea....
connect32 is what i change all my script to. Its a bug in qlikview that hangs job, nothing you can do unless you can upgrade to latest version.