* Fast publish post - be nice..

In my Cloud OS demonstration environment recently I had a host in the cluster reporting “Needs Attention” status and refreshing the host cluster failed with “error 2912”.

The Hyper-V Host was in “Needs Attention” status and performing any functions from VMM were failing.

Job summary example below:

_Error (2912) An internal error has occurred trying to contact the server.domain.net server: : .

WinRM: URL: [http://server.domain.net:5985], Verb: [ENUMERATE], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_PerfFormattedData_Tcpip_NetworkInterface], Filter: []

Unknown error (0xc0000bbf)_

2912

The basic tests (WinRM, DNS, Ping, Firewall etc) were indicating ‘communication’ was perfectly fine between host and VMM.

Found a post here that has several suggested resolutions and rebuilding the performance counters worked a treat for me.

From a administrator command prompt on the host:

lodctr /R

e.g. lodctr

By the time I switched back over to my VMM Console, the host status was “OK” so I refreshed the Host and all functionality resumed…

Not sure why this happened but the fix was fairly simple.

Cheers’ Dan

Daniel Apps

Hi, I'm Daniel Apps — AI platform enthusiast, unapologetic infrastructure nerd, and dad to two small humans. I write about infrastructure, AI industry topics, and the real-world chaos of modern IT.

More about me →

s