Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Polling engine keeps restarting and services status shows as Running

Polling engine keeps restarting and services status shows as Running

Updated April 17, 2017


The polling engine keeps restarting, but there is no visual indication that the services are crashing. The status of all services in the Orion Service Manager is displayed as Running but is displayed as Down in the Polling Engines page. The KeepAlive column in the Engines table indicates that polling has stopped and values are no longer updated.

The Windows Events (system) displays the following EventID from Microsoft-Windows-Kernel-General (source) which indicates a severe time change:



The event message displays the following:

The description for Event ID '1' in Source 'Microsoft-Windows-Kernel-General' cannot be found.  The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them.  The following information is part of the event:'2017-04-11T19:10:57.424000000Z', '2017-04-11T12:46:26.810505900Z', '1'


The time sequence in the SolarWinds Information Service (SWIS) v3 log also displays as backwards:

2017-04-11 14:09:55,170 [14] INFO SolarWinds.Orion.Core.Common.WCFChannelFactory`1 - (null) Channel NcmBusinessLayer to net.tcp://orion02:17777/orion/ncm/businesslayer Opened
2017-04-11 07:45:27,795 [14] WARN SolarWinds.Orion.Core.Common.WCFChannelFactory`1 - (null)     System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.


All Orion Platform versions


This behavior is caused by severe time changes that were applied automatically at a Kernel level by Windows Time Service (W32Time). These services receives time updates from an external source. This commonly happens in virtual environments where the host, which hosts the virtual machine, provides time update through its internal mechanisms.


Fix the time updates issue. As a workaround, stop and disable the Windows Time Service (W32Time) to prevent it from turning on after a server reboot.


Last modified