New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.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


Getting false alert for IIS App pool

Votes:

0

Your Vote:

Up

Down

Hi Team,

I have 3 web servers with several app pools that are being monitored through PRTG. I am getting error:

Unable to connect to the specified computer, or the computer is offline. (Performance Counter error 0x800007D0)
from the last 2 weeks someone from these servers randomly. When I checked on the server whole application was working fine. These alerts started coming on its own and after 2-3 hours they started resolving itself. Kindly let me know a permanent fix for it.

error-messages iis iis-app-pool webserver

Created on Jun 4, 2020 8:29:48 AM by  Sandeep (0) 1

Last change on Jun 4, 2020 1:53:20 PM by  Moritz Heller [Paessler Support]



11 Replies

Votes:

0

Your Vote:

Up

Down

Hi there,

Please check whether you can ping / telnet the device while the Sensor is in the down state.

Created on Jun 4, 2020 1:55:05 PM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Yes, I can ping the devices from PRTG server and it's an intermittent issue.

Created on Jun 4, 2020 5:30:46 PM by  Sandeep (0) 1



Votes:

0

Your Vote:

Up

Down

The error does not necessarily mean that the target host totally went down the drain, it just means the sensor cannot perform the required action, which basically is establishing a connection to the remote registry service on the target host.

Please check if remote registry service is running on the target host. Also try restarting the probe service to see if that helps.

You can also take a look at this article: https://kb.paessler.com/en/topic/47263-my-windows-sensors-do-not-work-when-using-direct-performance-counter-access-what-can-i-do

Created on Jun 5, 2020 7:00:04 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

My host hasn't gone down completely, only app pools get down and automatically get up after 1-2 hours. Please guide

Created on Aug 18, 2020 1:02:09 PM by  Sandeep (0) 1



Votes:

0

Your Vote:

Up

Down

Hi there,

Please take a look at our extensive WMI Troubleshooting Guide: https://kb.paessler.com/en/topic/1043-my-wmi-sensors-don-t-work-what-can-i-do

Please check if you tried everything noted there.

Created on Aug 18, 2020 1:54:39 PM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

It's an intermittent issue, not a permanent issue as everything is working fine now. And it's specifically with Windows IIS Pools as when I get alerts for APP pool notification, Ping, services, disk, memory, CPU shows fine, up and running. So kindly suggest a solution to check IIS App Pool specifically.

Created on Aug 18, 2020 3:01:09 PM by  Sandeep (0) 1



Votes:

0

Your Vote:

Up

Down

Please let me know whether you checked the troubleshooting steps in the article and which error message is displayed.

Created on Aug 19, 2020 6:10:08 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Please find the below PRTG logs:

Date Time	Sensor	Status	Message
8/19/2020 15:20	App Pool Inside	Notification Info	State Trigger activated (Sensor/Source/ID: 3195/2326/1)
8/19/2020 15:20	App Pool Inside	Up	Running
8/19/2020 13:36	App Pool Inside	Notification Info	State Trigger activated (Sensor/Source/ID: 3195/2326/1)
8/19/2020 13:35	App Pool Inside	Down	Warning by lookup value 'Shutdown Pending' in channel 'Application Pool State'
8/19/2020 13:30	App Pool Inside	Warning	No data to return. (Performance Counter error 0x800007D5)
8/18/2020 16:19	App Pool Inside	Notification Info	State Trigger activated (Sensor/Source/ID: 3195/2326/1)
8/18/2020 16:19	App Pool Inside	Up	Running
8/18/2020 13:58	App Pool Inside	Notification Info	State Trigger activated (Sensor/Source/ID: 3195/2326/1)
8/18/2020 13:57	App Pool Inside	Down	Warning by lookup value 'Shutdown Pending' in channel 'Application Pool State'
8/18/2020 13:52	App Pool Inside	Warning	No data to return. (Performance Counter error 0x800007D5)
8/17/2020 12:15	App Pool Inside	Notification Info	State Trigger activated (Sensor/Source/ID: 3195/2326/1)
8/17/2020 12:15	App Pool Inside	Up	Running
8/17/2020 9:49	App Pool Inside	Notification Info	State Trigger activated (Sensor/Source/ID: 3195/2326/1)
8/17/2020 9:48	App Pool Inside	Down	Warning by lookup value 'Shutdown Pending' in channel 'Application Pool State'
8/17/2020 9:43	App Pool Inside	Warning	No data to return. (Performance Counter error 0x800007D5)
8/15/2020 19:26	App Pool Inside	Notification Info	State Trigger activated (Sensor/Source/ID: 3195/2326/1)
8/15/2020 19:26	App Pool Inside	Up	Running
8/15/2020 19:15	App Pool Inside	Notification Info	State Trigger activated (Sensor/Source/ID: 3195/2326/1)
8/15/2020 19:14	App Pool Inside	Down	Warning by lookup value 'Shutdown Pending' in channel 'Application Pool State'
8/15/2020 19:09	App Pool Inside	Warning	No data to return. (Performance Counter error 0x800007D5)
8/15/2020 14:09	App Pool Inside	Up	Running

Created on Aug 19, 2020 2:02:53 PM by  Sandeep (0) 1

Last change on Aug 20, 2020 6:34:49 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

According to these log entries, the Sensor works. However, it seems like that the Sensor receives no data for one scanning interval but receives values again if PRTG request them again. I recommend to increase the scanning interval to at least 5min to reduce such errors. Please note that WMI needs a lot of performance and therefore a high scanning interval is recommended.

Created on Aug 20, 2020 6:36:46 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I have checked, the current scanning interval is 60 seconds but if I will make I configure it to 5 minutes that will not make any difference. As when it gets down, it came up after 3 hours.

Created on Aug 20, 2020 3:38:14 PM by  Sandeep (0) 1



Votes:

0

Your Vote:

Up

Down

Hi,

Thank you for the update. Please send en email to "[email protected]" with the latest information so that we can continue troubleshooting. Please enter the ID "PAE2017952" in the subject of your email.

Created on Aug 21, 2020 8:28:34 AM by  Moritz Heller [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.