New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


WMI: Process not found (code: PE009) -- PerfCounter: No data to return. (Performance Counter error 0

Votes:

0

Your Vote:

Up

Down

This error is being encountered on a new server we've built to replace an old server. On the old server, the sensor works perfectly fine. Here is everything I've checked: OS version is the same - 2008 R2 (replacing physical server with vm) Cisco firewall ACLs are the same (both servers are in the same ACLs) Windows Firewall is turned off Tested using Powershell "Get-Counter" from the PRTG server, while logged in with the account that PRTG runs under: Get-Counter '\Process(*)\% Processor Time' -ComputerName servername Checked GPO results on both - nothing different

What am I missing?

Can someone at PRTG maybe explain EXACTLY how this sensor gets information? i.e. does it use .NET or Powershell or some other command under the hood?

Lastly, is it possible to use CIM, rather than WMI to check something like this?

perfcounter prtg wmi

Created on Apr 8, 2016 5:17:01 PM by  Peter Bollwerk (80) 1 1



Best Answer

Accepted Answer

Votes:

1

Your Vote:

Up

Down

We figured out the problem. For some unknown reason, when the server was built by our hosting provider, they added a registry entry to append the PID to processes in PerfMon. https://support.microsoft.com/en-us/kb/281884

I found that the old server did not have this registry entry. Once I deleted it on the new server, the sensors started finding the processes.

Created on Apr 12, 2016 4:50:25 PM by  Peter Bollwerk (80) 1 1



5 Replies

Votes:

0

Your Vote:

Up

Down

Hi,
The process sensor is a hybrid sensor. Either it gets its data via a WMI query over DCOM/RPC or if this is not possible it will try to get the data via perfcounters.
The WMI Connection can be tested using the WMI Tester. As regarding the perfcounters you can use perfmon, connect to the target host to see if you get any data.
PRTG basically works the same way those both tools do. Do you get correct readings with the WMI Tester/perfmon?
If you are in need to just connect and get data vie e.g. Powershell, you can use the EXE/Script Sensor (Advanced) to do so. It can execute Powershell natively.
Best regards

Created on Apr 11, 2016 2:16:34 PM by  Konstantin Wolff [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Using the WMI Tester and Perfmon directly from the PRTG server to query the target server both work just fine. So this makes it even stranger that PRTG is failing, if it relies on these same methods. I suppose I can write a custom PS script to do this, but I'd really rather not have to do that for every new server we deploy. What else can we do to troubleshoot this?

Created on Apr 11, 2016 4:43:50 PM by  Peter Bollwerk (80) 1 1



Votes:

0

Your Vote:

Up

Down

In this case this might be a permission issue. The Probe service runs with a local SYSTEM account of the machine whereas perfmon and the WMI Tester are executed in the context of your user. You might try changing the account the probe service is running under.
Best regards

Created on Apr 12, 2016 1:11:35 PM by  Konstantin Wolff [Paessler Support]



Accepted Answer

Votes:

1

Your Vote:

Up

Down

We figured out the problem. For some unknown reason, when the server was built by our hosting provider, they added a registry entry to append the PID to processes in PerfMon. https://support.microsoft.com/en-us/kb/281884

I found that the old server did not have this registry entry. Once I deleted it on the new server, the sensors started finding the processes.

Created on Apr 12, 2016 4:50:25 PM by  Peter Bollwerk (80) 1 1



Votes:

0

Your Vote:

Up

Down

Thanks for the heads up and sharing your solution!

Created on Apr 13, 2016 11:58:52 AM by  Konstantin Wolff [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.