Adding a host to System Center Virtual Machine Manager 2008 may fail with error 2912 / 0xc0000BBF
Published Feb 14 2019 09:38 PM 414 Views
First published on TECHNET on Aug 17, 2009

Over the past few months I have been seeing a couple of these cases come by where when you try to add a host to System Center Virtual Machine Manager 2008 it fails with the following message:

Error (2912)
An internal error has occurred trying to contact an agent on the server.
(Unknown error (0xc0000bbf))

Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

In addition, if you look in the Application Log you may see the following events:

WMI, Event 10
Event filter with query "select * from __instancemodificationevent within 30 where targetinstance isa 'Win32_PerfFormattedData_PerfDisk_LogicalDisk' and targetinstance.PercentFreeSpace < 1 and targetinstance.Name != '_Total'" could not be reactivated in namespace "//./root/CIMV2" because of error 0xc0000bbf. Events cannot be delivered through this filter until the problem is corrected.

WMI, Event 5612:
Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: HandleCount  Value: 12853 Maximum value: 12288 WMIPRVSE PID: 7232

In the VMM Debug View Trace , the following lines occur:

00004091 183.74186707 [7232] CLOSE called:
00004092 183.74189758 [7232] CLOSE: closing driver
00004093 183.87825012 [7232] DsOpenPerformanceData() Called
00004094 183.87858582 [7232] open failed
00004095 185.68054199 [8584] VSPSTATS: enum

00003787 158.73509216 [7748] 1E44.2084::08/12-14:59:07.773#19:Task.cs(246): Task failed error HostAgentFail (2912); HR: 0xC0000BBF with exception Microsoft.Carmine.WSManWrappers.WSManProviderException: An internal error has occurred trying to contact an agent on the server.
00003788 158.73509216 [7748] Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
00003789 158.73509216 [7748]    at Microsoft.Carmine.WSManWrappers.ErrorContextParameterHelper.ThrowTranslatedCarmineException(ErrorInfo ei, Exception ex)
00003790 158.73509216 [7748]    at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.RetrieveUnderlyingWMIErrorAndThrow(SessionCacheElement sessionElement, COMException ce)
00003791 158.73509216 [7748]    at Microsoft.Carmine.WSManWrappers.WsmanAPIWrapper.Enumerate(String url, String filter, Type type)
00003792 158.73509216 [7748]    at Microsoft.Carmine.WSManWrappers.WSManRequest`1.Enumerate(String url, String wqlQuery)
00003793 158.73509216 [7748]    at Microsoft.Carmine.WSManWrappers.WSManRequest`1.Enumerate(String url)
00003794 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.Adhc.WindowsHostDataProperties.GetNetworkAdapters(NetworkLocationAwareness nla)
00003795 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.Adhc.WindowsHostDataProperties.PopulateProperties()
00003796 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.Adhc.WindowsHostAbstractionLayer.GetHostProperties(HostData oldHostData)
00003797 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.Adhc.HostRefresher.GatherAllInformation(Host host, Object agentRefreshSyncObj, Guid taskID)
00003798 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.Adhc.HostRefresher.RefreshLockedHost(Host host, Guid taskID)
00003799 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.Adhc.RefreshVmHostSubtask.RunSubtask()
00003800 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
00003801 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.Adhc.AddHostTask.RunSubtask()
00003802 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
00003803 158.73509216 [7748]    at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
00003804 158.73509216 [7748] *** Carmine error was: HostAgentFail (2912); HR: 0xC0000BBF

Note: This behavior has also been seen with existing hosts that worked before but then start experiencing the issue when the host is refreshed.


This occurs when the performance counters are corrupt on the host you are trying to add.


To rebuild extensible counters, third-party counters, and all other performance counters follow these steps:

1. Open an elevated Command Prompt window.

2. At the command prompt, type the following command, and then press ENTER:


3. At the command prompt, type the following command and then press ENTER:

lodctr /R

Note: In this command, "R" is uppercase.

4. At the command prompt, type exit , and then press ENTER to close the Command Prompt window.

Justin Luyt | Senior Support Engineer

Version history
Last update:
‎Mar 11 2019 08:14 AM
Updated by: