Login

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

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

Votes:

0

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

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

Best Answer

Accepted Answer

Votes:

1

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:

Save this script in PRTG's install directory into subfolder "....Custom Sensors\EXEXML"
Add an EXE/Script ADVANCED sensor to the IIS device in PRTG
Select the script from the dropdown
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]

29 Replies

Votes:

0

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

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

Votes:

0

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

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

Created on Apr 12, 2018 11:53:24 AM

Votes:

0

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

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

Votes:

1

Hello again,

restarting probe solve the issue

Created on May 3, 2018 11:36:16 AM

Votes:

0

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

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

Votes:

0

Please drop us a mail via [email protected], 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

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

Accepted Answer

Votes:

1

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:

Save this script in PRTG's install directory into subfolder "....Custom Sensors\EXEXML"
Add an EXE/Script ADVANCED sensor to the IIS device in PRTG
Select the script from the dropdown
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

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

Votes:

0

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

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

Votes:

0

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

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

Votes:

0

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]

Votes:

0

I just had this issue on a new installation, removing the sensor and adding it back seemed to solve the issue. Not a solution, since it will probably break again the next time the server is rebooted, but worth noting here I think.

Created on Jan 26, 2020 9:19:25 AM

Votes:

0

Thanks for the notice. Did this happen on the native Sensor or with the script?

Created on Jan 27, 2020 2:46:29 PM by Stephan Linke [Paessler Support]

Votes:

0

I am having the same issue with the native sensor, figured this would have been fixed by now if its been an issue for over a year.

Created on Jul 13, 2020 3:16:32 PM

Votes:

0

Hi Nick,

I'm very much afraid to tell you that there are no news regarding a fix right now as it would require a major rework. Are you able to get the sensor running with the provided script?

I'm sorry I don't have better news for you.

Kind regards,
Andreas Günther
Tech Support, Paessler AG

[email protected]

Created on Jul 14, 2020 10:30:00 AM by Andreas Günther [Paessler Support]

Votes:

1

Hi Andreas,

What do you mean it would require a major rework? You have a workaround that works and all we need is a new sensor type that uses your workaround. We're at almost two years now to monitor a basic Windows function (is my WEB SERVER performing) and you've had a workaround for almost two years that it seems could just be a new sensor.

Created on Apr 15, 2021 12:04:08 PM

Votes:

0

Hello, I checked internally and we don't have updates on this at the moment. So far the workaround is the only way.

Created on Apr 20, 2021 4:10:16 AM by Jonathan Mena [Paessler Technical Support]

Votes:

0

Can the image be re-uploaded showing the parameters for the Custom Sensor? I am unable to see it.

Created on Jul 7, 2021 4:28:11 PM

Votes:

0

The image is still available. It is hosted in imgur.com so make sure your machine has access.

Configuration of the sensor

Created on Jul 12, 2021 9:27:49 PM by Jonathan Mena [Paessler Technical Support]

Votes:

0

Hello

Im looking for the solution for this, is it still a manually created powershell script.

We have like 150 + app pools on a lot of different servers so do we need to make this manually for all app pools ?

This issue was reported like 5 years ago and STILL not fixed in the main sensor for application pools surveillance.

if this is correct that this issue is still here , then Paessler obviously not taking the customers seriously.

Created on May 16, 2022 8:42:44 AM

Votes:

0

Same issue here. Still waiting for a fix other than the workaround.

PRTG Cluster, one node shows all IIS sensors running fine, the other one shows No data to return. (Performance Counter error 0x800007D5) after we rebooted the IIS server this weekend. I will reboot the PRTG node reporting errors later today, that usually fixes thing until the next time..

Created on Sep 26, 2022 5:57:45 AM

Votes:

0

Is there any fix for this. I am having the same issues and the workaround will not be possible as I have hundreds of app pools to monitor.

Created on Apr 14, 2023 2:14:49 PM

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.