When troubleshooting QlikView service related issues, such as service crashes, web server disconnects or failing tasks, log files are the natural source of information around the root cause of a problem. Logging may, however, not be set up correctly to record all the required information.
This article provides an overview on how to best set up QlikView service logging when looking for root causes of disturbances.
Should be set to Normal logging Only change to Debug logging if the QlikView Management Console itself is presenting strange behaviour when communicating with other services or is only partially loading. Set back to normal after troubleshooting is finished, as the debug logs create large files.