Skip to end of metadata
Go to start of metadata

Title: 

Generating  a Windows Crash Dump using Windows Task Manager to help troubleshoot SUP 2.X unresponsive issues.

Purpose: 

To show the reader how to generate a Crash Dump using Windows task manager in order to help trouble shoot  Issue with the Windows programs running as part of SUP.

Overview: 

 There are times when there are issue where the SUP Server is unresponsive and  a Windows Stack trace is needed to determine what  the  Windows process  is  processing at this time.    There are better ways to get a stack trace, for example using  Managed Stack Explorer (MSE), but in some cases the issue happens in a production environment and customers do not have the time to use the steps outlined in the wiki with instructions outlining how to obtain an MSE and need to recover the server ASAP.  This process is quick, you just need to get about 5 dumps  of  the specific Windows process in a 60 second time interval.  The SUP Messaging Server Windows Process  are obmo.exe, obServiceManager.exe, AdminWebServices.exe (No longer in SUP 2.2 and Greater).  The example below show the OBMO.exe process.  

Solution:

When the SUP Server is unresponsive (Hanging) you need to bring up Windows Task Manager,  select the Process you want to create a dump for then Right Click and select  "Create Dump File" .


Then  a pop up will appear showing you the Location of the Dump file ,  all of the one I have seen for Windows 7 seem to always go to  \user\userID\AppData\local\ProcessName.DMP

The  Dump created is a Windows Crash Dump and  you will need WinDbg  to open it.

 

  • No labels