Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Customer Service > Customer Service - Knowledgebase Articles > Unable to List Resources on a Node or Agent

Unable to List Resources on a Node or Agent

Updated August 1st, 2017


The following error occurs when adding WMI Nodes or clicking on List Resources: is currently down, unreachable, or provided  credentials are not valid



  • NPM version 10.3 or later
  • SAM version 6.0  or later
  • Orion Core 2012 or later
  • Windows Server 2008 -2008 R2



Any of the following can cause the error:

  • Corrupted WMI Repository 
  • Missing Registry Keys 

Click Here for: Troubleshooting WMI Repository Issues Help (© 2016 Virtually Boring , available at , obtained on November 4, 2016.) 


  1. Open Regedit.exe
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PerfProc\Performance
  3. Review the setting “Disable Performance Counters”, a 1 indicates it is disabled. 
  4. If it is disabled the “exctrlst.exe” tool can be used to enable PerfProc.  
  5. After Rebooting, the below WMI query should return a value. 
    SELECT * from Win32_PerfRawData_PerfProc_Process where NAME <> '_Total' 
  6. Verifying with WBEMTEST from the Orion server that WMI is now working.


List Resources should now correctly display on the Node.


Click here for Full Thwack Post


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.



Last modified