QlikView log files – SR patching impact on it

Verbosity level may change after SR patching so if you notice any kind of swelling on log file after that. Pls. make sure to do necessary change in config.exe file.

This scenario happened to me once, log files were growing enormously (~10 GB). Eventually I have to do correct value for Debuglog to “False” which got changed to “True” after SR patching.

****************************************************************************
On the QV Server open the config file:

QVDistributionService.exe.config
… this is normally found in C:\Program Files\QlikView\Distribution Service\

In this file look for the section marked by:

There are two keys that should both be set to false:

****************************************************************************

Note: To know more about QlikView log files, watch this video from QlikTech. https://www.youtube.com/watch?v=iMBDASFxA3M

Facts of QlikView log files

Given below are the services that have log files associated to it,  this post is written considering QlikView 10 and 11.

1. QVS
2. QDS
3. QVWS
4. DSC
5. QMS

** QlikView Server Setting Service is one exception. Since this is related to IIS, separate log is not provisioned.  Another important point note here, only in QlikView 11 this service is available not in version 10.

By default QlikView log files are Tab delimited.

Paths:

Default paths for log files are:

1. C:\ProgramData\QlikTech\QlikViewServer
2. C:\ProgramData\QlikTech\DistributionService
3. C:\ProgramData\QlikTech\WebServer\Log or C:\inetpub\logs\LogFiles\W3SVC1 (if IIS is used)
4. C:\ProgramData\QlikTech\DirectoryServiceConnector\Log
5. C:\ProgramData\QlikTech\ManagementService\Log

 

Only QVS and QDS can be configured on QEMC/QMC (QEMC is obsolete in QV11) for the rest of the logs we have to edit their respective config files under “c:\program files” .

For instance, in order to change QMS log files path, C:\Program Files\QlikView Management Service\QVManagementService.exe.config has to be edited accordingly.

 

 Highlighted line needs to be updated with new path.

Archival Process:

Only QDS has automated archival process of 30 days, for remaining services it should be part QlikView Admin’s periodic activity.

Verbosity/Logging level:

QVS Event Log can be configured any one of the below verbosity.

** QlikView Event log is very useful log in order to debug server availability issues.

• Low – log only Errors
• Medium – logs Error and Warning
• High – logs Error, Warning and Information

 

Other log files also has also similar kind of Verbosity/Logging level set-up. Thumb rule is to have higher level of verbosity/logging level during debugging and bring it back to normal once the issue is fixed, but again this is subjective to the environment.

**Verbosity level may change after SR patching so if you notice any kind of swelling on log file after that, please make sure to do necessary change at  config.exe file accordingly.