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 > Network Performance Monitor (NPM) > Trap service is stopped

Trap service is stopped

Created by Alexander Aguilar, last modified by Aileen de Lara_ret on Oct 06, 2016

Views: 396 Votes: 1 Revisions: 7

Updated September 14, 2016


This article provides brief information and steps to resolve the issue when the trap service is stopped.


NPM 11.x


This occurs when the service is not started or UDP port 162 is being used by another application.


Trap service not started

  1. Confirm that Simple Network Management Protocol is installed on the SolarWinds server having the problem. Otherwise, install it.
  2. Open Services on the SolarWinds server having the issue.
  3. Disable and stop the SNMP Trap Service.
  4. Enable and Start the SolarWindsTrapService.


UDP port 162 is used by another application

  1.  Open a cmd.exe on the SolarWinds server having the issue.
  2. Enter netstat -aop udp  and check which PID is using upd port 162.
  3. Open Task Manager.
  4. Go to Details and search for the application using PID 22484 (for our example) and End Task.
  5. Start the SolarWindsTrapService in the Service Manager.


Last modified
18:28, 5 Oct 2016