I just upgraded from 14.2.something to 14.3.10.2422. Four existing working sensors based on "Hyper-V Virtual Machine" now fail with the following error.

WMI: Access violation at address 00AC8880 in module 'PRTG Probe.exe'. Read of address 0000000C -- PerfCounter: The handle is not a valid PDH object. (Performance Counter error 0xC0000BBC)

Other WMI sensors on the same host work just fine. I've tried restarting the Probe service, but that didn't work.

I've also tried adding the sensor back again, but when I go to do that, none of the virtual machines shows up in the sensor creation panel, so I can't create any sensors.

Remember, these were sensors that were previously working prior to the upgrade. All I did was upgrade the probe software and they stopped working.

Article Comments

Hello,

thank you very much for your KB-Post. Are these 2nd Generation Hyper-VMs by any chance? If so, I'm afraid this is an issue in PRTG which should be fixed with a coming 14.x.11 stable build. Please bear with us then.

best regards.


Jul, 2014 - Permalink

I am using 2012R2, my generation two machines have this problem too.

Looking forward to the new release!


Jul, 2014 - Permalink

I think that 2nd gen stuff is for Server 2012 *R2*. Our VM host is only Server 2012.


Jul, 2014 - Permalink

WMI: Access violation at address 00AC8880 in module 'PRTG Probe.exe'. Read of address 0000000C -- PerfCounter: The handle is not a valid PDH object. (Performance Counter error 0xC0000BBC) I have just upgraded to latest version - now running PRTG Network Monitor 14.3.10.2422+ I too had Hyperv VM's being monitored quite happily before but now two of them have the error above. The Windows host server is running Windows 2012 Standard (not R2) Please could you update me when a fix has been identified Thanks Paul


Jul, 2014 - Permalink

PLease bear with us until version 14.x.11 is released. It should fix these Access Violations on the Hyper-V Sensors. I'm sorry, but there is no Work-Around until then.


Jul, 2014 - Permalink

Hi there,

Is this still a problem? Because I still get this error on my PRTG 14.3.10.2422 is there no fix for this version?


Jan, 2015 - Permalink

Version 14.3.10 is still older than 14.x.11 (please note the 3rd digit of the version number). And actually we are already on version 15.1.13. Please update, and the issue should be fixed.


Jan, 2015 - Permalink

Thank you Torsten, I will do this and see.


Jan, 2015 - Permalink