Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Troubleshooting Tools > Collect a process dump

Collect a process dump

Table of contents
Created by Richard Casey, last modified by Harry Griffiths on May 07, 2017

Views: 29 Votes: 1 Revisions: 13

Overview

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

Environment

Applies to all SolarWinds products

Steps

  1. Download and install Procdump from below location

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

     
  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
04:21, 7 May 2017

Tags

Classifications

Internal Use Only