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 > Syslog service unexpectedly starts or stops

Syslog service unexpectedly starts or stops

Updated October 5th, 2016


This article provides brief information and steps to resolve the issue when the SolarWinds Syslog services unexpectedly starts or stops causing the Windows Event log to fill up with errors and see the below error in corresponding log file. Restarting Services / Reboot of Server has no affect and IPv6 was not enabled

2016-11-14 11:35:02,528 [UDPListenerThreadIpv6] ERROR SolarWinds.Orion.Common.SWEventLogging - Syslog Service Unhandled Exception Only one usage of each socket address (protocol/network address/port) is normally permitted
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at System.Net.Sockets.UdpClient..ctor(IPEndPoint localEP)
   at SolarWinds.Syslog.UdpPacketListener`1.ListenForSyslogPackets(Boolean isIpv6, IPEndPoint localEndPoint, IRunState runState)
   at SyslogService.SyslogService.ListenForUDPPacket(Object ipv6)
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, Conte 


Orion Core products  2015

NPM 10.7


The error is caused by another server listening on port UDP 514 OR

It could also be caused by recent attempts to upgrade to NPM and a roll back on a VM environment.


It could also be due to broken syslog service


Check what service is running on port 514

Open CMD and enter nestat -abn.

Stop Syslog service via Service Manager. 


If none of the above helps, and you don't see any services using port 514 and syslog restart when look at Orion Service Manager, then doing a repair of Orion Core should fix the problem or reinstall of syslog service



Last modified