Network Management

Orion Platform Troubleshooting using Windows Event Logs

Filter Windows Events so you can focus on Application, System and SolarWinds Events. Correlate errors found in Windows Events with other problems found in the other log files

First published date

7/17/2019 3:14 PM

Last published date

7/17/2019 3:14 PM

Overview

Log Located in:       

  • Orion  Server: 
    • Go to Start > Run > eventvwr
  • Diagnostics: 
    • SolarWindsDiagnostics.zip\EventLogs
  • Check:
    • Application, System, Solarwinds logs
  • Tips:                 
    • Filter down to the meaningful errors, it is easy to filter down 5000 Events to just few dozen errors.
    • Filter Down to WARNING and ERROR Messages, also check the timestamp.
    • Once you find an error, if needed search the relevant logs for more info. E.g: SQL Timeouts, out of disk space errors
  • Note - When to ignore errors:
    • Most SQL Errors in Eventvwr can be ignored as its normal to see the odd timeout.
    • Filter out Errors & Warnings for the OldAlertingService, SWService, SyslogService, TrapsServices.
    • Reason for so many bogus timeouts can be explained as follows:
      • those services are older Win32 Processes and are more 
      • those services in particular hit SQL every second or minute due to number of syslogs\traps or\and alerts config.
      • For example if Orion user has 20 million syslogs a day, 20-30 of these having a warning is not a huge issue.
    • Examples
      • Service was unable to open new database connection when requested.
      • SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.Service was unable to open new database connection when requested.
      • There was an error updating the Engine Keep alive record
      • Error Detail-System.Data.SqlClient.SqlException (0x80131904): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
      • There was an error reading the setting value for SWNetPerfMon-Settings-DHCP EnableRDNS from the database.
    • Example of real errors:
      • This may have occurred because all pooled connections were in use and max pool size was reached.
      • The database transaction log is full and cannot be grown. Please check for available Space.
      • Database-Maint.exe Another instance of Database Maintenance is running on this computer. Only one instance of Database Maintenance may run at a time.

Product section

Orion Platform