Network Management

Collector Logs Indicate Nodes Are Not Polling in SolarWinds Platform

This article outlines a workaround to resolve the polling issue identified in the Collector logs.

First published date

2/12/2025 8:44 AM

Last published date

12/5/2025 9:28 PM

Overview

This article provides an overview of an issue where nodes are not being polled. Upon investigation, no errors are visible in the web console, and restarting the SolarWinds services does not resolve the problem.

In cases like this, the issue is often linked to the collector. The below error message causing the polling failure can be found in the collector logs:

 

IPAM.BusinessLayer.log
2024-12-11 02:18:41,144 [EntityWatcher] ERROR SolarWinds.Orion.Core.SharedCredentials.ReadOnlyCredentialDAL - Unable to find credential with ID = 468, owner = Orion and credentialType = SolarWinds.Orion.Core.SharedCredentials.Credentials.UsernamePasswordCredential
2024-12-11 02:18:41,144 [EntityWatcher] ERROR SolarWinds.Collector.BusinessLayer.EntityWatcher - EntityCreator process failed IPAM.DnsZone.Creator
SolarWinds.Orion.Core.SharedCredentials.Exceptions.CredentialNotFoundException: Unable to find credential with ID = XXX, owner = Orion and credentialType = SolarWinds.Orion.Core.SharedCredentials.Credentials.UsernamePasswordCredential

Collector.Service.Log
2024-12-11 03:32:45,285 [211] ERROR SolarWinds.Orion.Core.SharedCredentials.ReadOnlyCredentialDAL - Unable to find credential with ID = XXX, owner = Orion and credentialType = SolarWinds.Orion.Core.SharedCredentials.Credentials.UsernamePasswordCredential
2024-12-11 03:32:45,301 [211] ERROR SolarWinds.Collector.PollingController.PollingPlanResolver - Resolve polling plan failed!! We will try to resolve it in next round

 

 

Product section

Orion Platform

Cause

The root cause is that IPAM cannot authenticate with DNS servers due to missing or incorrect credentials. This authentication failure prevents IPAM from scanning and updating DNS servers, causing the collector and job engine to stop working, which in turn affects message queuing and polling of nodes. 

Resolution

  1. Check the IPAM BL and collector logs for any errors related to credential issues. Look for the Credential ID in the logs (in this case, ID = 468).

Example:

2024-12-11 03:32:45,285 [211] ERROR SolarWinds.Orion.Core.SharedCredentials.ReadOnlyCredentialDAL - Unable to find credential with ID = 468, owner = Orion and credentialType = SolarWinds.Orion.Core.SharedCredentials.Credentials.UsernamePasswordCredential
2024-12-11 03:32:45,301 [211] ERROR SolarWinds.Collector.PollingController.PollingPlanResolver - Resolve polling plan failed!! We will try to resolve it in next round

 

  1. Open database manager and navigate to the IPAM_DnsServerDetails table.
  2. Search for the Credential ID within the error message to identify the DNS servers associated with the issue. For example, in this case, the Credential ID is 468, and the following DNS servers are encountering problems:

 

    1. Open the NodesData table in the database and check the NodeID to determine which nodes are impacted by the credential issue.
    2. Go to the IPAM DNS server pages and check the Last Update column. If it is not updating, this may indicate a problem with the DNS servers or credentials.
    3. Edit the target node to apply the correct credentials.
    4. Scan the DNS server scan on the target node and wait until the Last Update column is refreshed.
    5. Restart both the Main and APE SolarWinds services.
    6. If the Last Update column is still not updating after applying the correct credentials, then follow the below steps.
      1. Delete the affected DNS server node and re-add it. 
      2. Restart both the Main and APE SolarWinds services once more to ensure that changes are applied.