Qlik Community

Ask a Question

Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Join this live chat April 6, 10AM EST - QlikView to Qlik Sense REGISTER

GFlags - Find out what killed silently a windows process

Alexis_Touet
Support
Support

GFlags - Find out what killed silently a windows process

Our Qlik services have been developed with safeguards to record in our logs the cause of a service restart, and/or generate a dump file when a crash occurs.

However, in some very rare occasions, a process can be killed silently by another process, and when you check your Qlik product logs to have a better understanding of what happened, you do not find any error or warning, just entries that confirm the service was stopped and started. 

 

Environment:

Qlik Sense Enterprise on Windows
QlikView
Qlik NPrinting
Microsoft Windows 

 

How to debug a silent crash/termination?

Debugging tool for Windows has a nice utility called gflags.exe which can be used to find out who/what caused the process kill.

After you download and install the Debugging tool for windows, launch gflags.exe from the installation directory. It requires admin privileges to open so be sure to be administrator on the computer where you are launching this.

Follow the below instructions to configure Windows process exit monitoring.

  1. Launch gflags.exe from Windows Debugging tool kit installation directory
  2. Switch to “Silent Process Exit” tab
  3. Type the name of the process that you want to monitor. In my case, I have given notepad.exe
  4. Press tab and check the box “Enable silent process exit monitoring”
  5. Click OK to complete.
 

The next time your process is killed silently you will see  in Application event log a new  event ID 3000 from source “Process Exit Monitor” which should provide the information on what / who killed your Qlik process. 

 

Important note:

This tool can also be used to force windows to generate a mini dump what our service is stopped.
We highly recommend this feature too so we can provide a mini dump to our R&D teams if we need further analysis.

Related Content

https://techibee.com/sysadmins/find-out-who-killed-a-process-in-windows/2286

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/registry-entries-for-silent-proce...

 

Labels (2)
Version history
Revision #:
4 of 4
Last update:
‎2020-12-28 05:13 AM
Updated by:
 
Contributors