Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
A file that is scheduled to be reloaded takes awful lot of time before getting into failed status.
When I tried to reload the same file in developer/client, it gets done quickly and without any errors or warnings.
I checked all the logs but I'm unable to point out the possible cause for this issue.
Given below are few lines from the logs :
---------------------------------------------------
03.05.2010 14:28:40.4158680 Warning The QlikView Engine working with document "D:\ABC\test.qvw" hasn't been responding for 1800 seconds. It will be killed.
03.05.2010 14:28:40.4783680 Warning The QlikView Engine is Reloading, it will be killed (Please ignore logged errors about the kill).
03.05.2010 14:28:40.4783680 Information Killing the QlikView Engine. ProcessID=8160
03.05.2010 14:28:40.5096180 Error The operation was aborted.
03.05.2010 14:28:40.5877430 Information Closed the QlikView Engine successfully. ProcessID=8160
03.05.2010 14:28:40.5877430 Information Initializing Reload (0), Finished (1826313)
03.05.2010 14:28:40.5877430 Error Reload failed.
03.05.2010 14:28:40.5877430 Information Closed the QlikView Engine successfully. ProcessID=8160
03.05.2010 14:28:40.6033680 Information Initializing (0), Finished (15)
03.05.2010 14:28:40.6033680 Error Reload failed. Distribution skipped.
03.05.2010 14:28:40.6033680 Error The task "Reload of test.qvw" failed. ErrorCount=3
------------------------------------------------
Few points
1. OS and QV server installed are both 32-bit.
2. I've enabled the log for the file but it has no useful information about the possible error.
Please help!
It looks like you're running up against the "Max seconds at zero CPU usage" limitation (see QEMC --> System --> Distribution Service --> Advanced tab). The only difference between reloading through Publisher and reloading through Desktop is which user account is being used. So a good troubleshooting step would be to logon to Windows using the Publisher user account and then try to reload manually through Desktop. My guess is that this will give you some errors that will then be useful for further troubleshooting...
Regards,
I have hit this problem a couple of times and it always comes back to a permissions issue. Turn on the log file in the qlikview document. Run it from publisher and go look at the Log file. It will tell you what you don't have access to
Thanks for your inputs Vlad.
We managed to get this sorted out by using OLE DB connection instead of ODBC.
Strange but it worked!
Thanks for your comments Jsomsen.
We had actually turned the logging on but couldn't figure much out of it. We then thought of trying OLE DB connection and it worked!!
Need to make sure that when you setup ODBC connections that you set them up as System DSN and not User DSN. If you use User then you have to setup the connection for each users. System is for anyone using the machine.