Orion Syslog Server not receiving messages

10/15/2018 4:49 PM

6/17/2022 6:23 AM

This article provides reason why the Orion Syslog Server is not receiving any error messages.

Orion Platform

The most common reasons are listed below.
 

• The syslog service is not running. Open the Start->SolarWinds Network Performance Monitor->Advanced Features->Shutdown NetPerfMon tool and ensure that the Syslog Service is running.
• The devices are not configured to send syslog messages on UDP port 514. For assistance with configuring the devices to send syslog messages, we recommend checking with the vendor.
• A filter/alert is removing the syslog messages as they are received. Check the actions associated to the filters/alerts by clicking on View->Filters Alert/Rules, editing each alert and viewing the actions listed under the Alert Actions tab.
• The Orion SQL server is case sensitive. SolarWinds does not currently support case sensitive SQL servers. If you are seeing the following error message within the Event Viewer on the OS within the SolarWinds.Net folder, then most likely the SQL server is case sensitive. 

Event Type: Error
Event Source: SyslogService
Event Category: None
Event ID: 5013
Date: 7/27/2005
Time: 5:10:02 PM
User: N/A
Computer: PAORCW01
 

Description:

There was an error reading my EngineID from the Database.
Will use the default of 0 Error Detail: Must declare the variable '@ENGINEID'.
 

You can verify that the SQL Server is case sensitve by opening the SQL Enterprise Manager, right-clicking on the Orion SQL Server, selecting Properties, and looking at the Server collation field. If _CS_ is included in the value, then the server is case sensitive.