Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Collect a process dump

Collect a process dump

Table of contents

Overview

This article describes how to collect a process dump. The Development Team requests this information to allow them to analyze and determine the reason why a process or service crashed.

Environment

Applies to all SolarWinds products

Steps

  1. Download and install Procdump from the following location:

    https://technet.microsoft.com/et-ee/sysinternals/dd996900.aspx

    (© 2017 Microsoft, available at technet.microsoft.com, obtained on April 25, 2017)
     
  2. Identify the affected process ID or process name from the Task Manager.
     
  3. Using the command prompt, browse to the folder where Procdump is installed and enter the following command:
    procdump -MA -E PID
    OR
    procdump -MA -E PROCESSNAME

 

     

Note:
When you run the command without -E, it will collect the current process dump without waiting for the process or service to crash.
 This command will create a process dump for the named process when it crashes and store it in the folder from where Procdump was executed (i.e. folder where Procdump is installed).

Example Usage
procdump -ma -e 2789      (which is the PID of Syslog Service)
procdump -ma -e SolarWinds.InformationService.ServiceV3.exe
procdump -ma -m 8100 SolarWinds.BusinessLayerHost.exe

Auto Capture
procdump -ma -i

Turn off Procdump
procdump -u (stop collecting dumps)
 

Delete the value from Debugger under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug
 

Memory leak:


Gather diagnostics and send the memory dump to the SolarWinds Development team for further investigation.

 

Note: It is recommended to grab a memory dump when it reaches 6GB and one when it reaches 10GB to compare.

 

  1. Download and install Procdump to the polling engine with memory leak issues
    (© 2017 Microsoft, available at technet.microsoft.com, obtained on April 25, 2017).
  2. After the download, open two command prompts run as an administrator.
    On the first command prompt, run the following command:
    <folder>\procdump.exe -ma -m 6000 SolarWinds.InformationService.ServiceV3.exe
    On the second command prompt, run the following command:
    <folder>\procdump.exe -ma -m 10000 SolarWinds.InformationService.ServiceV3.exe

 

See the Capture a memory dump article for an alternative method.

 

 

Last modified

Tags

Classifications

Public