In order to evaluate failed or slow QlikView document reloads it is very valuable to see how the reload was executed. This can be accomplished by catching a log during the script reload (script log), which for example shows the execution timeline and the amount of data loaded. Possible error messages from the reload process will also be logged and thereby making trouble shooting easier.
However, this log is NOT enabled by default. It is always a good idea to provide a script log when reporting issues with failed reloads to QlikView Support. At the same time it can be a valueable tool for application developers trying to trouble shoot issues during development work.
Note: The following settings will also apply if document is reloaded through QlikView Publisher, which may give valuable information on failing tasks.
Environments:
The script logging can be setup to generate time stamped files for each reload, or one logfile which only contains the latest reload.
The files are created in .log format and can be opened in any text editor (notepad, notepad++, etc..).
Multiple log files, one for each reload (recommended):
Only one log file that contains the latest reload (NOT recommended if you reload in the middle of the night and will overwrite the failed document log):
Please, also check QlikView 12: Distribution Service apparently not generating document log until reload completion; if the reload fails, the document reload log may reside in the source document or QVB folder.