Hello Shane,

would you please take a look at registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PerfProc\Performance and here the value of "Disable Performance Counters". It should be set to "0".

Best regards, Thomas

Thanks. That helped one of the machines. I still have two others that it didn't. I have changed/verified the setting on both and rebooted both machines.

Anything else I should be looking for?

Both machines have a tick in that box for PerfProc.

Similar problem here, but instead of "Classes not found" we have

Instance(s) not found "Win32_PerfRawData_PerfProc_Process\1220"

right after updating to PRTG 12.

Changing the registry key as said above, switched the error to

Unknown Error in "Win32_Process".

This happened with the wmiservicesensor on only one machine. Other machines on the same probe have wmiservicesensor as well, an the machine with the error has other wmi sensors, which work.

Any ideas?

Have you tried adding the sensor anew?

Creating a new sensor on our affected machines results in the same error message:

Class(es) not found: "Win32_PerfRawData_PerfProc_Process"

Have the same problem ranging from old Win 2K to new Win 2008 R2. Tried all of the above and tried to recreate sensors. Still not working.

Can you revert to working PRTG 9 version after upgrade to 12?

Just wanted to report the same exact problem here. Only one server is affected, even though we use this sensor type on many servers. None of the above resolved the issue.

We have the same problem after update to version 12. It's only one machine affected.

Hi,
we are working on a fix with high priority but at the moment we cannot give a precise release date.
Best regards

Same Problem here. About 1000 WMI-Sensors and only the sensors for one machine are not working. "Win32_PerfRawData_PerfProc_Process"

Hi all,
please perform a upgrade to the most recent version of PRTG 12.2.1.2029. We added a switch to the sensor settings called "CPU Usage". Set the same to "Don't monitor CPU Usage" for all affected sensors. This can be done with multi-edit and should fix the issue for now. Additional we are working on a further solution.
Best regards

Is this one of the "new" style updates that does not interrupt the system? IS there "downtime" associated to this update? Thanks!

LN

Hi,
the update is normal update and there should be no downtime.
Best regards

I just wanted to report that I followed the directions above (I actually updated to v12.2.1.2041) and the error is *not* occurring anymore, as you advised.

I'm not sure how the CPU usage factors into this sensor, as it's not one of the metrics listed under channels. In either case, it works now and that's good enough for us.

The new build and setting change also fixed our issue.

New setting worked on Win 2008, not working on Windows 2K at all, have 3 different W2K and none can be monitored using WMI-Service sensor. Disk space an CPU load work however...

Hi,
please note that W2K is not officially suppported anymore since PRTG 7 which was released in 2009. We are not testing on W2K machines and therefore we cannot guarantee that monitoring of the same will continue working. Albeit that there is a workaround either using a Custom WMI Sensor as described here or you may use a external sensor called Service Status from PRTG Addons.
Best regards

I am having this issue on core version 13.1.2.1463. I've check the RPC and DCOM services on the server as well. Server version is Windows Server 2008 Standard Version 6.0.6002 SP2 Build 6002.

I am getting Class(es) not found: Win32_PerfRawData_LocalSessionManager_TerminalServices".

I have plenty of other servers with the same version and domain that are not having this issue. The registry key above does not exist on this server and this issue remains even after a server restart. Any help or update is appreciated.

Just found a difference with working servers for WMI sensors. The sensors that are working monitoring terminal service sessions are on 2008R2 servers the one that isn't working is on a 2008 Standard sp2 server. What is the issue here? Is there a different sensor type I should be using for this version of server?