The various components of QlikView and Qlik Sense may have crashed without specific indication on why. Data may be missing because logging was disabled, or no resource data collection was set up.
For further monitoring, and to potentially catch the failure better should it happen again, the following should be considered:
- Enable the appropiate logging and set it to a high enough level.
QlikView Server logging can be set to High
verbosity and to be split daily for ease of review
Enable Audit logging to capture user interaction
See the Qlik Online Help
for more details on our products logging levels and settings.
- Enable Performance Logging on the Windows host.
This will provide information should the root cause be a resource related issue, such as RAM shortage, CPU overload, disk access issues, etc...