Network Management

List Resources keeps spinning in the SolarWinds Platform

This article explains what needs to be done to get List Resources to return resources. List Resources keeps spinning and never returns the list of resources.

First published date

11/7/2018 3:36 AM

Last published date

4/24/2026 8:10 PM

Overview

In some environments, list resources on a node may take a very long time.  This can occur when pressing List Resources directly or when Adding a Node and also if the number of resources exceeds 8000.


Product section

Orion Platform

Cause

  • DNS resolution of APE failing
  • SWIS Port is not open between APE/MPE and AWS

Resolution

Please make sure SolarWinds Port Requirements are met between the Server hosting website and Server Polling the nodes.

Scenario1: List resources not working for any agent based nodes(windows and Linux) on the polling engine.

If the issue is affecting almost all nodes on a Polling engine, check Orionweb.log on the Main poller; if the list resources operation was performed from the web console on the Main server. If an Additional web server URL is used, then check the orionweb.log on that server.

You may see DNS resolution errors to the FQDN or NetBIOS hostname of the APE, if so
1. Open c:\windows\system32\drivers\etc\hosts
2. Add an entry for both FQDN and NetBIOS short hostname entries
3. Save it and test List Resources again.

If the above scenario does not apply, then continue to the steps below.

Scenario 2:

  1. Edit the node and see the polling method and what polling engine it is using
  2. Check to see if the polling engine is up or down.
  3. If SNMP and the polling engine is up, do an SNMP walk from the polling engine to the node, to see how long that action takes.
  4. If the polling engine is down and using the primary poller, check whether the c:\ProgramData\Solarwinds\Logs\Orion\BusinessLayerHost.log or c:\ProgramData\Solarwinds\Logs\Orion\Core.BusinessLayer.log has any error messages.
  5. If no timely error messages and all services are up on the server of the primary poller or the additional polling engine, try stopping and restarting the SolarWinds Orion Module Engine.
  6.  If using an Additional Polling Engine and it is down, determine why the node is down. Stop and restart services if nothing pops out.
  7. You may need to reinstall Job Engine and Collector Services. 
  8. If the above steps did not work, re-add the node.
  9. If the polling method is SNMP, try all versions v1,v2, and v3, and make sure SNMP is configured on the device side before testing it with SolarWinds.