<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article How To Catch Small Memory Dump File With Windebug in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Catch-Small-Memory-Dump-File-With-Windebug/ta-p/1713440</link>
    <description>&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Environment:&lt;/H4&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;LI-PRODUCT title="QlikView" id="qlikView"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Note:&amp;nbsp;&lt;/STRONG&gt; 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&amp;nbsp;&lt;A title="QlikView Server Is Crashing? Get A Crash Dump" href="https://community.qlik.com/t5/Knowledge/QlikView-Server-Is-Crashing-Get-A-Crash-Dump/ta-p/1714951" target="_blank" rel="noopener"&gt;QlikView Server Is Crashing? Get A Crash Dump&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Install Windebug on the QlikView Server&lt;BR /&gt;&lt;SPAN&gt;32bit:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi&amp;nbsp;" target="test_blank"&gt;http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi&amp;nbsp;&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;64bit:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi&amp;nbsp;" target="test_blank"&gt;http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi&amp;nbsp;&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Run Windbg as an administrator&amp;nbsp;when&amp;nbsp;&lt;/SPAN&gt;QlikView Server is running without problems.&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;Use File &amp;gt; Attach to process and select the QVS.EXE process&lt;BR /&gt;NOTE: The QVS.EXE process will halt until next steps&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Enter the letter “g”in the bottom of the window and press &amp;lt;Enter&amp;gt;. &lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;The window will then show “Debuggee is running...”&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;From the Debug Menu, select “Break” (or CTRL+Break) to halt the QVS process&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Create a dump by entering “.dump /m c:\DumpFile1.dmp” in the debugger&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;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.&amp;nbsp;&lt;BR /&gt;There is no need to save any information in workspace (if prompted for this)&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;STRONG&gt;Reference&lt;/STRONG&gt;&lt;BR /&gt;Create Dump File, &lt;SPAN&gt;Microsoft MSDN&lt;/SPAN&gt;;&amp;nbsp;&lt;A href="https://msdn.microsoft.com/en-us/library/windows/hardware/ff562428(v=vs.85).aspx" target="_blank" rel="noopener"&gt;https://msdn.microsoft.com/en-us/library/windows/hardware/ff562428(v=vs.85).aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jan 2022 14:18:49 GMT</pubDate>
    <dc:creator>ToniKautto</dc:creator>
    <dc:date>2022-01-21T14:18:49Z</dc:date>
    <item>
      <title>How To Catch Small Memory Dump File With Windebug</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/How-To-Catch-Small-Memory-Dump-File-With-Windebug/ta-p/1713440</link>
      <description>&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Environment:&lt;/H4&gt;
&lt;P&gt;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;LI-PRODUCT title="QlikView" id="qlikView"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Note:&amp;nbsp;&lt;/STRONG&gt; 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&amp;nbsp;&lt;A title="QlikView Server Is Crashing? Get A Crash Dump" href="https://community.qlik.com/t5/Knowledge/QlikView-Server-Is-Crashing-Get-A-Crash-Dump/ta-p/1714951" target="_blank" rel="noopener"&gt;QlikView Server Is Crashing? Get A Crash Dump&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Install Windebug on the QlikView Server&lt;BR /&gt;&lt;SPAN&gt;32bit:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi&amp;nbsp;" target="test_blank"&gt;http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi&amp;nbsp;&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;64bit:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi&amp;nbsp;" target="test_blank"&gt;http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi&amp;nbsp;&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Run Windbg as an administrator&amp;nbsp;when&amp;nbsp;&lt;/SPAN&gt;QlikView Server is running without problems.&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;Use File &amp;gt; Attach to process and select the QVS.EXE process&lt;BR /&gt;NOTE: The QVS.EXE process will halt until next steps&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Enter the letter “g”in the bottom of the window and press &amp;lt;Enter&amp;gt;. &lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;The window will then show “Debuggee is running...”&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;From the Debug Menu, select “Break” (or CTRL+Break) to halt the QVS process&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Create a dump by entering “.dump /m c:\DumpFile1.dmp” in the debugger&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;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.&amp;nbsp;&lt;BR /&gt;There is no need to save any information in workspace (if prompted for this)&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;STRONG&gt;Reference&lt;/STRONG&gt;&lt;BR /&gt;Create Dump File, &lt;SPAN&gt;Microsoft MSDN&lt;/SPAN&gt;;&amp;nbsp;&lt;A href="https://msdn.microsoft.com/en-us/library/windows/hardware/ff562428(v=vs.85).aspx" target="_blank" rel="noopener"&gt;https://msdn.microsoft.com/en-us/library/windows/hardware/ff562428(v=vs.85).aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jan 2022 14:18:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/How-To-Catch-Small-Memory-Dump-File-With-Windebug/ta-p/1713440</guid>
      <dc:creator>ToniKautto</dc:creator>
      <dc:date>2022-01-21T14:18:49Z</dc:date>
    </item>
  </channel>
</rss>

