TrueSight Capacity Optimization (TSCO) Capacity Agent (formerly BMC Performance Assurance) data collection on windows is failing to connect to WMI. The following messages are reported in the [hostname]-bgscollect.exe-noInstance.log file. These message only appear at the agent startup. If the agent has been running for a while these messages may not appear in the collected logs. Restart the agent to see the messages if the issue still exists.

Wed Aug 31 01:00:00 2011 bgscollect.exe (10880:6804) debug, WMICollect::InitializeWMI() starts
Wed Aug 31 01:00:00 2011 bgscollect.exe (10880:6804) Connect wmi namespaceServer OK
Wed Aug 31 01:00:00 2011 bgscollect.exe (10880:6804) debug, WMICollect::ConnectWMI() starts
Wed Aug 31 01:00:00 2011 bgscollect.exe (10880:6804) debug, WMICollect::DoConnectWMI() starts
Wed Aug 31 01:00:00 2011 bgscollect.exe (10880:6804) ConnectServer OK
Wed Aug 31 01:00:00 2011 bgscollect.exe (10880:6804) ConnectWMI failed at AddEnum, error: 0x80041010
Wed Aug 31 01:00:00 2011 bgscollect.exe (10880:6804) Error code 0x80041010 => Invalid class

The key message is the 'ConnectWMI failed at AddEnum, error: 0x80041010' error. That indicates that although the host was able to establish the initial connection to the WMI interface on the host (the 'ConnectServer OK') it then wasn't able to access the System Statistics data via the WMI interface.

These messages will appear in the bgscollect.exe log files. Since these 4 data groups must exist in the UDR data for Analyze to process, these errors are another symptom of the issue.

Thu Dec 17 00:00:07 2020 bgscollect.exe (1516:1344) using Performance Registry for System
Thu Dec 17 00:00:07 2020 bgscollect.exe (1516:1344) Error - could not add group NT System Statistics with instance noInstance
Thu Dec 17 00:00:07 2020 bgscollect.exe (1516:1344) using Performance Registry for Processor
Thu Dec 17 00:00:07 2020 bgscollect.exe (1516:1344) Error - could not add group NT Processor Statistics with instance noInstance
Thu Dec 17 00:00:07 2020 bgscollect.exe (1516:1344) using Performance Registry for Memory
Thu Dec 17 00:00:07 2020 bgscollect.exe (1516:1344) Error - could not add group NT Memory Statistics with instance noInstance

Applies To:

TrueSight Capacity Optimization (Capacity Agent) 11.5, 11.3, 11.0, 10.7, 10.5, 10.3, 10.0
BMC Performance Assurance for Servers 9.5, 9.0, 7.5.10
 

Section I: 'winmgmt /resyncperf' and 'exctrlst'

Step 1

To resolve this issue, run the following command on the Windows 2003 or later machines that aren't data into TSCO via the Gateway Server VIS parser ETL, Visualizer, or Perceiver:
winmgmt /resyncperf

This command will re-sync the list of performance objects available through WMI with the performance objects available in the Performance Registry.

Step 2

Restart the Perform Agent on the machine.

Once the Perform Agent has been stopped and restarting (which should also stop and restart the running bgscollect process) the data collection problems should be corrected which should allow Analyze to properly process the and report data in Visualizer, Perceiver, and BMC TrueSight Capacity Optimization.

If the problem hasn't been resolved, it could mean that the problem is within the performance registry itself (not within WMI) and the PerfOS system groups currently aren't available.

Step 3

Run 'perfmon' on the machine and see if it is possible to access the 'System' performance object. If that isn't listed it likely means that the PerfOS DLL has been disabled within the Performance Registry by the OS. This sometimes happens when the OS mistakenly thinks it has detected a problem.

Step 4

If the System performance object isn't available via Perfmon, you can re-enable the performance dll via the Extensible Counter Control tool that is part of Windows 2003 Service Pack 2 Support Tools package (http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=15326).

Alternately, the following Microsoft KA describes how to re-enable performance DLLs within the registry directly:
  https://support.microsoft.com/en-us/help/2554336/how-to-manually-rebuild-performance-counters-for-windows-server-2008-6

Step 5 

Either:
  (a) Run the tool and in the 'Extensible Performance Counters' section find the performance DLL that provides the system metric groups.
- or -
  (b) Follow the steps to access the performance registry directly

Step 6

Either:
  (a) In the Extensible Performance Counters tool select those Performance DLL entry. The 'Performance Counters Enabled' checkbox will be unselected. Click it to enable the counter.
- or -
  9b) Follow the steps in the Microsoft KA to enable the performance DLLs in the performance registry directly.

The standard performance DLLs to have enabled are:
PerfDisk (perfdisk.dll)
PerfNet (perfnet.dll)
PerfOS (perfos.dll)
Perfproc (perfproc.dll)
Tcpip (Perfctrs.dll)

Step 7

Stop and restart the Perform Agent.

To stop the agent, use the 'Stop Agent' GUI via:
Start => Program Files => BMC PATROL => Perform => Stop Agents

To restart the agent, use the 'Collect Data Wizard' GUI via:
Start => Program Files => BMC PATROL => Perform => Collect Data => Query Information from a running collect process => OK

Section II: If the problem persists
Typically the above steps will resolve the "ConnectWMI failed at AddEnum, error: 0x80041010" error and in most cases if it doesn't resolve the problem it is worth validating that the steps have been run correctly.
But, once it has been validated that the steps have been run correctly, another possible option would be to rebuild the Performance Registry via the 'lodctr /r' command.
The command is described in this Microsoft article: http://technet.microsoft.com/en-us/library/bb490926.aspx.  To rebuild the Performance Registry run the 'lodctr /r' command as an Administrator.  The output should look something like this:
>lodctr /r
Info: Successfully rebuilt performance counter setting from system backup store
WARNING: You should consult with your system administration team before running this command since it will overwrite all Performance counter registry settings and Explain text
 Additional Information
Often it is useful to be able to reproduce the error outside of the BPA product -- this can be particularly true when engaging another team in an environment to debug the Windows OS problem further.  A good test for this error would be to attempt to obtain performance data via WMI from these machines using the Windows PowerCLI.

So, you run:
> powershell

Then in Powershell at the "PS >" prompt you run the following command to test the remote WMI connection:

measure-command {Get-WmiObject Win32_PerfRawData_PerfOS_System | Out-Default}

The expectation is that this command would fail on any machine generating the "ConnectWMI failed at AddEnum, error: 0x80041010" because that message indicates that the PerfOS performance object doesn't appear to be available via WMI.