Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

QlikView 12: Distribution Service is not generating document log until reload completion

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Daniele_Purrone
Support
Support

QlikView 12: Distribution Service is not generating document log until reload completion

Last Update:

Oct 11, 2022 4:32:28 AM

Updated By:

Sonja_Bauernfeind

Created date:

Feb 26, 2017 4:00:19 AM

While a reload is in process, the document reload log cannot be found in the expected QlikView Distribution Service's location.

 

QlikView Distribution Service (Publisher reloads)


The document reload log is generated locally on the QlikView Distribution Service node handling the reload task. This means the file is stored locally in C:\ProgramData\QlikTech\QlikViewBatch 

Once the reload is completed, the document log is copied to the Source Document folder and QDS Application Data folder.

The purpose of this is to avoid continuously writing log entries to remote folders. 

To monitor document logs during reload, these logs can be found at C:\ProgramData\QlikTech\QlikViewBatch.

Temporary logs in this folder will be moved when the reload is done. 

 

QlikView Desktop client

For QlikView Desktop, the temporary script log is written to C:\ProgramData\QlikTech\QlikView while the reload is in progress. Once the reload is done, the log is copied to the same path with the qvw document.

 

Details


Document log optimization for QlikView Publisher

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 they 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.

For QlikView Desktop, parameters LocalScriptLogging and ScriptLogFolder can be changed in settings.ini file located under C:\Users\<UserName>\AppData\Roaming\QlikTech\QlikView. These parameters can also be altered using Easter Egg in QlikView: Help > About QlikView... > right-click the QlikView logo at the bottom left corner of the "About QlikView" dialogue.

Labels (1)
Version history
Last update:
‎2022-10-11 04:32 AM
Updated by: