Network Management
SolarWinds Trap service is stopped because another application is using UDP port 162
This article provides brief information and steps to resolve the issue when the trap service is stopped.
First published date
Last published date
Overview
The following error message can also be seen in the TrapService.log (C:\ProgramData\SolarWinds\Logs\Orion).
TrapService.log:
ERROR TrapService.TrapService - The service is unable to bind to port 162. Please stop the other trap manager.
[StartupThread] ERROR SolarWinds.Orion.Common.SWEventLogging - Unable to register with SNMP Trap Service for IPv6 SNMP Trap reception.
The following windows service is running: SNMP Trap
Which uses UDP Port 162
Product section
Cause
A non-SolarWinds application is already listening to UDP port 162 blocking the SolarWinds Trap Service to run.
Resolution
- Open CMD and run the command below
- Take note of the PID listed in the right side of the result
- Open Task Manager and under the Services tab, identify the service using the PID
- Uninstall(or disable) the service
- Click Start > Control Panel > Add or Remove Programs.
- Click Add/Remove Windows Components.
- Click Management and Monitoring Tools, confirm it is checked, and then click Details.
- Confirm the Simple Network Management Protocol is checked, and then click OK.
- If Simple Network Management Protocol was not checked, complete the Windows Components installation wizard.
- Click Start > Control Panel > Administrative Tools > Services
- Confirm the SNMP Trap Service is Disabled.
- If the SNMP Trap Service is not Disabled, right-click SNMP Trap Service, and then click Stop.
NOTE: This solution will allow the SolarWinds Trap Service to use UDP port 162 and listen for trap messages uncontested by other applications.