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 > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Trap service is stopped because another application is using UDP port 162

Trap service is stopped because another application is using UDP port 162

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

Views: 2,842 Votes: 1 Revisions: 7

Updated September 14, 2016

Overview

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

Environment

NPM 11.x

Cause 

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

Resolution

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

Tags

Classifications

Public