Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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:
- Qlikview Desktop, all versions
- Qlikview Server, all versions
Resolution:
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):
- Open QlikView desktop client
- Open the QlikView application that should be logged
- Go to Settings > Document Properties...
- Go to General tab
- Check the "Generate Logfile" checkbox
- Check the "Timestamp in Logfile Name"
- Press OK to save the settings and close the dialog
- Each reload will now generate a log file named as the QVW file and the timestamp of the reload in the same folder as the QVW file
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):
- Open QlikView desktop client
- Open the QlikView application that should be logged
- Go to Settings > Document Properties...
- Go to General tab
- Check the "Generate Logfile" checkbox
- Press OK to save the settings and close the dialog
- Each reload will now regenerate a log file named as the QVW file in the same folder as the QVW file
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.
Related Content:
Hello @KD_
Assuming you want to change it for the QlikView client when doing local reloads, you can attempt to change the ScriptLogFolder in the settings.ini.
Default location: C:\Users\YOURUSER\AppData\Roaming\QlikTech\QlikView
If you mean the Publisher logs created by the server, these log locations can be changed as well. See How To Change QlikView Service Logs/AppData To An Alternate Location.
All the best,
Sonja
