we had quite a few of those rather vague errors where one could easily reload an app in the client, but the automated reload failed.
Just a guess:
- Maybe the server cannot access one or other of the files involved? Check the paths - not from your machine, but from the server, the paths do look different there.
- Have you already had a ´look at that app's own logfile (activate it in the document_properties and wait for another server-side reload) -> that is usually easier to read and understand.
- Log on to the server, trigger that app, watch the script_execution_window for the exact command where it breaks and check that in_depth.
No problem. I had this prepared but wasn't sure whether you knew already about server logs. Here we go:
To obtain DocumentLogs, turn on "Generate log file" in your document (see Settings->Document properties->General) Since you don't know beforehand which document will fail, you'll have to enable this option in every document.
Let your scheduler perform a few tasks until one of them fails. Then visit the logs directory and check the DocumentLog of the failed QVW for errors.
Distribution logs are to be found on the QlikView server in C:\ProgramData\QlikTech\DistributionService\1\Log This folder contains a subdirectory for every day on which tasks were started. In that subdirectory you'll find folders for every started task. The folder name includes a timestamp to keep successive executions of the same task apart. Inside such a folder you'll find a TaskLog and (if script execution logging was enabled) a document log.
The latter may provide you with a more detailed cause for execution failure.