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


Is there a workaround for "No data to return." in IIS App Pool Sensors?

Votes:

0

Your Vote:

Up

Down

Getting multiple App Pool sensors on a server with this error. The weird thing is, all applications are started and running fine - the other handful of App Pool sensors are also reporting fine still, why would these one's not be? I've verified Remote Registry service is running.

Thanks for any help you can give.

error performance-counters sensor

Created on Feb 28, 2017 7:15:35 PM by  hayitsnik (0) 1

Last change on Aug 15, 2018 8:27:32 AM by  Stephan Linke [Paessler Support]



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

The following script will act as a workaround for the native sensor, which sometimes has connection troubles. While the problem looks simple to fix, it's more than a mere bugfix. It's buried deep within the Performance Counter framework we're using and is a lot of work to fix (with unforseen caveats). Hence we came up with the following.


Caution The culprit however is, that in order to work properly you need to configure PRTG's Probe service to run in the context of a user that is allowed to access the targeted hosts (by default it runs in the context of "Local System"). So usually this should be a domain admin, that way you make sure that all sensors requiring Windows credentials work properly.


It will basically do the same/retrieve the same metrics as the IIS App Pool sensor, but using a powershell script to do so. Here's what to do to get the custom sensor running:

  1. Save this script in PRTG's install directory into subfolder "....Custom Sensors\EXEXML"
  2. Add an EXE/Script ADVANCED sensor to the IIS device in PRTG
  3. Select the script from the dropdown
  4. Set parameters as shown in the image attached, while the name behind "instance" reflects the name of the desired app pool.

Configuration of the sensor

Let it run for some time additionally to the standard IIS App Pool sensor and let us know if this runs more "stable" than the IIS App pool sensor or if both are failing around the same time.

In case you have trouble getting the powershell sensor to run, please find here more details what to take care of: Guide for PowerShell-based Custom Sensors


Kind regards,
Stephan Linke, Tech Support Team

Created on Aug 15, 2018 8:21:07 AM by  Stephan Linke [Paessler Support]

Last change on Aug 15, 2018 8:21:40 AM by  Stephan Linke [Paessler Support]



18 Replies

Votes:

0

Your Vote:

Up

Down

Do they work intermittently? Or always down? Are they in an idling state perhaps?

Created on Mar 1, 2017 11:18:18 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I have the same issue.

After a reboot of a VM, a handful of the App Pool sensors will we Up, but the majority will be down. It tends to last for a few hours. Sensor interval is 60s.

Error is:

No data to return. (Performance Counter error 0x800007D5)

Created on Mar 27, 2017 9:26:50 PM by  gregpakes (0) 1



Votes:

0

Your Vote:

Up

Down

Did you already try to recreate the sensor to see if that resolves the issue?

Created on Mar 28, 2017 8:35:55 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I am having this same issue, anyone fix it yet?

Created on Apr 12, 2018 11:53:24 AM by  Perley Dexter (0)



Votes:

0

Your Vote:

Up

Down

Hi there,

Did you already try to restart the corresponding target host to resolve the issue? Has the sensor been recreated already?


Kind regards,
Stephan Linke, Tech Support Team

Created on Apr 13, 2018 10:02:49 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello i have same problem as described above. we have 2 nodes PRTG cluster and after reboot monitored VM most of app pool senzors are down. sort of down - first prtg node shows them as UP, but second PRTG node has problem - No data to return. (Performance Counter error 0x800007D5)

already try to delete those senzors and create new ones - same issue appear

Created on May 3, 2018 9:02:58 AM by  vonhovic (0) 1



Votes:

0

Your Vote:

Up

Down

Hello again,

restarting probe solve the issue

Created on May 3, 2018 11:36:16 AM by  vonhovic (0) 1



Votes:

0

Your Vote:

Up

Down

Thanks for the update, glad the issue is resolved now :)


Kind regards,
Stephan Linke, Tech Support Team

Created on May 3, 2018 11:46:33 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Dear PRTG - Support Team,

we have same issue (No data to return. (Performance Counter error 0x800007D5)) with 6 WMI Netzwerkadapter/Network Sensors. Those sensors are set up to monitor different Virtual Server. Until last week sensor on those machines runs fine, since 10 days - no data error. Nothing was changed on VMs or Network, they just turned to error state.

To solve the problem, we tried to - restart target Virtual Server, - restart prtg probe, - restart prtg server,

Nothing of them works to reanimate the sensor. But creating a new (redundant) WMI Netzwerkadapater sensor, works. New sensor works fine and deliverst gereen working state.

How to reanimate the sensor, in case we are still interested in historical monitoring data?

Thanks.

Created on May 17, 2018 9:40:27 AM by  dgadmin (0)



Votes:

0

Your Vote:

Up

Down

Please drop us a mail via support@paessler.com, referring to this thread. I'll send you the workaround script then.


Kind regards,
Stephan Linke Tech Support

Created on May 18, 2018 8:41:06 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I have the same issue vonhovic described:

PRTG cluster, 2 nodes.
After rebooting a monitored webserver (VM), the first node picks up all App Pool sensors.
However, the second node for most of the App Pool sensors gives the error "No data to return. (Performance Counter error 0x800007D5)"

Unfortunately I cannot afford to restart the probe on the 2nd node each and every time a VM restarts.
So if there would be a proper solution, that'd be greatly appreciated!

Created on Aug 14, 2018 5:46:22 PM by  Corné van den Bosch (40) 1 1



Accepted Answer

Votes:

0

Your Vote:

Up

Down

The following script will act as a workaround for the native sensor, which sometimes has connection troubles. While the problem looks simple to fix, it's more than a mere bugfix. It's buried deep within the Performance Counter framework we're using and is a lot of work to fix (with unforseen caveats). Hence we came up with the following.


Caution The culprit however is, that in order to work properly you need to configure PRTG's Probe service to run in the context of a user that is allowed to access the targeted hosts (by default it runs in the context of "Local System"). So usually this should be a domain admin, that way you make sure that all sensors requiring Windows credentials work properly.


It will basically do the same/retrieve the same metrics as the IIS App Pool sensor, but using a powershell script to do so. Here's what to do to get the custom sensor running:

  1. Save this script in PRTG's install directory into subfolder "....Custom Sensors\EXEXML"
  2. Add an EXE/Script ADVANCED sensor to the IIS device in PRTG
  3. Select the script from the dropdown
  4. Set parameters as shown in the image attached, while the name behind "instance" reflects the name of the desired app pool.

Configuration of the sensor

Let it run for some time additionally to the standard IIS App Pool sensor and let us know if this runs more "stable" than the IIS App pool sensor or if both are failing around the same time.

In case you have trouble getting the powershell sensor to run, please find here more details what to take care of: Guide for PowerShell-based Custom Sensors


Kind regards,
Stephan Linke, Tech Support Team

Created on Aug 15, 2018 8:21:07 AM by  Stephan Linke [Paessler Support]

Last change on Aug 15, 2018 8:21:40 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

We have the same issue, sensors work perfectly well until the server is rebooted then some, not all sensors remain in an error state forever. The account we use is a domain admins. The only solution is to restart the probe.

Created on Feb 20, 2019 11:15:49 AM by  ahuggard (0)



Votes:

0

Your Vote:

Up

Down

Or use the script approach above. Unfortunately, fixing this issue is requiring a lot of work under the hood which we can't do as of now, as there are other things we need to take care of first. Sorry about the ongoing issues regarding this.


PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Feb 20, 2019 11:30:08 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Stephan,

It does look like you already know what the problem is.
Care to share? So we can come up with a better workaround than start using custom scripts?

Kind regards.

Created on Mar 22, 2019 1:48:29 PM by  Corné van den Bosch (40) 1 1



Votes:

0

Your Vote:

Up

Down

We really don't, Corné :( It remains to be seen if a refactoring of the modules will resolve the issue. In the meantime, the custom scripts are the best option for the time being.


PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Mar 25, 2019 7:57:35 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Dear all, I'm impacted by this bug and support team pointed me to this solution. I adapted the scritp to my needs, and it seems working correctly, but is still a workaround. Is it possible to know if there is a planned deadline for stable solution? Why should we use a custom script: app pool monitoring should be one of your a major focus, and the first segnalation is two years old.

Kind regards.

Created on Mar 29, 2019 11:55:19 AM by  chriva (0)



Votes:

0

Your Vote:

Up

Down

No ETA on a possible solution, unfortunately. As it's a major rework, affecting thousands of installations and Sensors :( Sorry.


PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Created on Mar 29, 2019 12:12:12 PM by  Stephan Linke [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.