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 > SolarWinds Syslog Service Stopping

SolarWinds Syslog Service Stopping

Table of contents

Updated August 11, 2016

Overview

This article provides a step by step guide on how to resolve issues related to SolarWinds Syslog Service stopping.

Environment

All Orion Modules including NPM 11.5.3 and NPM 12.0

Steps

1. From the Orion Server, open CMD

2. Type netstat -ano | findstr 514

 

This is what the results would look like: (check sample result below)

 

C:\netstat -ano | findstr 514

UDP 0.0.0.0:514 *:* 3500

UDP [::]:514 *:* 3500

 

3. Take note of its PID

4. Open the Windows Task Manager

5. From the Windows Task Manager, click on the Processes tab

6. Go to View and then click on Select Columns

7. Look for the PID (Process Identifier), put a check on it and then click Ok

8. Sort the PID then look for the PID that you found under UDP 0.0.0.0:514 *:* e.g. 3500

9. See what services is running for that PID, if you don't know the service using the PID, right click on it and select End Process

10. Open the Orion Services Manager (Start > All Programs > SolarWinds Orion > Advanced Features) and start the SolarWinds Syslog Service

 

 

Last modified

Tags

Classifications

Public
/*]]>*/