Network Management
Determine if a shutdown or restart event is causing Solarwinds service to stop or fail
How to determine if a shutdown or restart event is causing Solarwinds service stop or failure. This error found in the AlertingService.log file indicates that that a shutdown event occurred. To confirm whether this is indeed caused by a shutdown event, the Windows Event logs can be consulted. An informational message in the System logs with a source of User32 and event ID of 1074 with the general message:
First published date
Last published date
Overview
When trying to track down whether services are crashing or being caused by a shutdown or restart event in Windows, it is useful to look for the following error in the AlertingService.log files:
ERROR SolarWinds.Alerting.Service.AlertingService - Error while stopping service: System.InvalidOperationException: UpdatePendingStatus can only be called during the handling of Start, Stop, Pause and Continue commands.
at System.ServiceProcess.ServiceBase.RequestAdditionalTime(Int32 milliseconds)
at SolarWinds.Alerting.Service.AlertingService.DoStop()
This indicates that a command other than start, stop, pause or continue is in process and implies that a restart or shutdown signal has been initiated by a process or user.
This can be very useful in determining whether a genuine crash occurred or if Windows Updates or a script has caused the entire system to restart.
Product section
Resolution
This error found in the AlertingService.log file indicates that that a shutdown event occurred. To confirm whether this is indeed caused by a shutdown event, the Windows Event logs can be consulted. An informational message in the System logs with a source of User32 and event ID of 1074 with the general message:
"The process *.exe has (hostname) initiated the restart of computer hostname on behalf of user context\username for the following reasons: Shutdown event description
Shutdown type: *
Please also look for Windows Update service activity in the Event viewer.