Getting false alert for IIS App pool

Hi there,

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

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

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

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

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.

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.

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

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

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.

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.

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.

Hi, I have also same "efects" in my web server. I think that it is normal behavior that application pool stops and start itself later. Is there any news about this issue? BR Eero

Hi,

if the WMI App Pool Sensors do not work reliably, you can also try the workaround, as explained here.

Kind regards,
Matthias Kupfer - Team Tech Support