Applications Systems

How to determine the reason of Event "Server configuration polling failed on node 'xxxx'" in SCM

This is to discuss an issue when receiving a Event "Server configuration polling failed on node 'xxxx" in SolarWinds Server Configuration Monitor (SCM). This event can cause confusion because it does not provide detailed information about the cause of the failure.

First published date

9/30/2025 10:25 PM

Last published date

12/6/2025 3:03 PM

Overview

This article discusses an event that is triggered when SCM polling fails on a node during configuration collection. While the event verbiage itself appears generic, the cause details are available within the SCM Node subview under Configuration Details. 

Product section

Server Configuration Monitor

Resolution

To determine the reason for the event:

 

  1. Navigate to the affected node in the SolarWinds Web Console.
  2. Go to the Server Configuration Monitor subview. Configuration Details Widget.
  3. Review the error or warning message displayed. This will provide specific insight into why polling failed (e.g., “Access denied,” “File is Inaccessible","Script Error"). 

  1. Click on the profiles with issues to further check the details.

If a report is needed to find these events, run the following SWQL query:

SELECT PEE.TimeStamp, N.DisplayName AS NodeName, PE.DisplayName AS ElementName, P.Name AS ProfileName, PEE.Message AS ElementErrorMessage FROM Orion.SCM.Results.PolledElementErrors PEE INNER JOIN Orion.SCM.ProfileElements PE ON PEE.ElementID = PE.ElementID INNER JOIN Orion.SCM.Profiles P ON P.ProfileID = PE.ProfileID INNER JOIN Orion.Nodes N ON N.NodeID = PEE.NodeID