How To Catch Small Memory Dump File With Windebug

[ToniKautto]

Advanced troubleshooting memory dump files can sometimes be required when investigating QlikView or Qlik Sense on-premise engine crashes. Below are instruction on how to catch a small memory dump file with Microsoft Windebug tool. 

Environment:

Qlik Sense Enterprise on Windows 

QlikView 

Note:  QlikView has a built-in memory dump functionality since 11.20 SR13. The below is an alternate method, but not considered a needed procedure. For more information on obtaining a dumb using QlikView feature see QlikView Server Is Crashing? Get A Crash Dump 

1. Install Windebug on the QlikView Server
   32bit: http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi 
   64bit: http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi 
2. Run Windbg as an administrator when QlikView Server is running without problems.  
3. Use File > Attach to process and select the QVS.EXE process
   NOTE: The QVS.EXE process will halt until next steps 
4. Enter the letter “g”in the bottom of the window and press <Enter>.
5. The window will then show “Debuggee is running...” 
6. From the Debug Menu, select “Break” (or CTRL+Break) to halt the QVS process 
7. Create a dump by entering “.dump /m c:\DumpFile1.dmp” in the debugger 
8. Repeat steps 5-7 in order to create a couple of dump files with a minute or so between, and at the same time replicate the issue. 
   There is no need to save any information in workspace (if prompted for this)

Reference
Create Dump File, Microsoft MSDN; https://msdn.microsoft.com/en-us/library/windows/hardware/ff562428(v=vs.85).aspx