Node status Critical with “SNMP polling is failing: "" or “WMI polling is failing: "" message in SolarWinds Platform

2/20/2026 9:21 PM

3/30/2026 8:22 PM

After upgrading to SolarWinds Platform 2026.1 or later, the Node status indicates polling issues feature can display status messages similar to:

• SNMP polling is failing: '<reason>'
• WMI polling is failing: '<reason>'

In some environments, the reason placeholder is empty, and the node details page shows:

• SNMP polling is failing: ''
• WMI polling is failing: ''

Typical characteristics:

• Node Status: Changes to Critical.
• Polling method: SNMP (network devices) or WMI/WinRM (Windows servers).
• ICMP/Ping: May still respond successfully.
• Environment impact: Seen on multiple nodes and/or multiple customers, not limited to a single device or site.

 

Important: The empty quotes do not mean there was no error. They mean polling failed, but the detailed reason text was not populated into the display template.

 

Internally, the product uses templates such as:

• SNMP polling is failing: '{0}'.
• {0} polling is failing: '{1}'.

and attempts to insert a friendly error description (timeout, invalid credentials, SNMPv3 error, etc.). In specific error conditions, the message helper returns an empty string, which results in the UI showing empty single quotes instead of a human‑readable reason.

Hybrid Cloud Observability

Functional cause

• The polling engine detects a failure when communicating with the device (for example, SNMP timeout, invalid SNMPv3 credentials, WMI/WinRM connectivity issues, or device returning invalid values).
• The failure is raised through the internal SNMP/WMI polling logic and Node status is set to Critical as designed.

Display / message cause

• For known error codes, SolarWinds uses localized, friendly messages such as “Request timed out – possible causes include network issues, incorrect community string or SNMPv3 credentials, or device not responding.” or specific SNMPv3 errors (invalid username, authentication failure, encryption failure, FIPS mismatch, etc.).
• For certain less common or unmapped error codes, the message helper is called with a flag that instructs it to only return text for known errors. When the error code is not in that list, the helper sends back an empty string instead of a description.
• The UI template still renders the status as:
  

  SNMP polling is failing: ''

  or
  

  WMI polling is failing: ''

  which is confusing for users.

This combination of real polling failure + missing display text is the root cause of the behavior described in this article.

To resolve this issue, please upgrade to SolarWinds Platform 2026.1.1 and above.  The expected behavior is a proper error message should appear to determine how to resolve the problem.  If the failure message remains blank after SolarWinds Platform 2026.1.1 or later, please create a new support ticket for further investigation.

Recommended troubleshooting when you see “polling is failing: ''”

Even though the reason text is empty, you should treat this as a genuine polling failure and perform standard connectivity and credential checks for the affected node.

1. Confirm basic connectivity
   • Ping the node’s IP address (for example, 10.10.10.25) from the polling engine server.
   • If ping fails, troubleshoot routing, firewall rules, or the device itself.
   • If ping succeeds, proceed with SNMP/WMI‑specific checks.
2. Run the built‑in polling tests
   • For SNMP nodes:
     • Go to Manage Node or Edit Node.
     • Open the node in the SolarWinds web console.
     • Verify the SNMP version, port, and community string or SNMPv3 credentials.
     • Click Test (or the equivalent SNMP test option).
   • For WMI/WinRM nodes:
     • Go to Manage Node or Edit Node.
     • Open the node in the SolarWinds web console.
     • Verify credentials, protocol, and port settings.
     • Run the appropriate WMI/WinRM test from the node/edit dialog.
   • Capture the results:
     • If the test shows a clear error (for example, timeout, access denied, SNMPv3 authentication failure), follow your standard SNMP/WMI troubleshooting procedures to correct the issue on the device or network.
     • If the test is successful but the node still shows “polling is failing: ''”, proceed to step 3.
3. Collect data for SolarWinds Support
   If you cannot identify a clear device or configuration problem, or if the Edit Node tests succeed, collect the following before opening a case:
   • Node details showing Critical status with exact text SNMP polling is failing: '' or WMI polling is failing: ''.
   • Results of Test from Edit Node (showing success or detailed error).
   • SolarWinds diagnostics from the affected polling engine(s) collected as close as possible to when the issue occurs.
   • Include the NodeID(s) and approximate timestamps (for example, 2026-02-19 10:15–10:30) where the status changed.
   • SolarWinds Platform version (for example, 2026.1.x).
   • Polling method (SNMP v2c, SNMP v3, WMI, WinRM).
   • Whether the issue is occurring for multiple nodes/devices or seems isolated.
     Provide this information when contacting SolarWinds Support so they can confirm whether the behavior matches the known empty reason display issue.
     • Screenshots 
     • Diagnostics
     • Environment details