Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
QlikView 12 Task - Log files are stored in a different location before being moved after a successful reload.
QlikView 12 and 12.10
QlikView 12.20 (November 2017) and up
An increase in app reload times was observed in QlikView 12 when document logging is enabled in the document settings. This increase is most significant when using QlikView Publisher, because log files are often written to a remote folder.
To mitigate against this increase in reload times, logs are now saved locally, by default, before they are copied to the remote app folder Local script logging can be controlled using the LocalScriptLogging= and the ScriptLogFolder= parameters.
These parameters can be added to the settings.ini file located by default in C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch.
If these parameters are not included in the settings.ini file, local script logging is enabled.
By default, logs are written locally to C:\ProgramData\QlikTech\QlikViewBatch before the are moved to the remote app folder.
If a reload crashes, the logs may be retrieved from this folder.
The ScriptLogFolder= parameter can be defined to set the folder logs are written to.
You can also disable local script logging by setting LocalScriptLogging= to 0.
With this setting disabled, logs are written directly to the remote app folder.
The default local logging behavior can also be achieved by adding the two parameter and setting LocalScriptLogging= to 1 and leaving ScriptLogFolder= empty.
See QlikView 12 SR 1 Release Notes for more details.
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.