manually and replace $IISStruct.ApplicationPool with the name of your application pool? Are you sure it is running? Try putting start mode in advanced settings on your app pool on AlwyasOn and see if that helps? Maybe setting idle timeout to suspend instead of terminate? If you are not using the app pool, it might shut down..
I am a Linux guy living in a Windows world right now and some of this is Greek to me. I attempted to just run the command and nothing came back. When I try the Application Pool name I get an error. Checking within IIS Manager the Application Pool is running.
You do not have the required permissions to view the files attached to this post.
Checking within IIS Manager the Application Pool is running.
It does not mean that if the application pool is running it has a corresponding w3wp.exe process. Please check you advanced settings of your application pool. Check idle timeout and Start mode.
Ok, so the Start Mode was onDemand and I changed it to AlwaysRunning. The Idle Time-out (minutes) is set at 900 and the Idle Time-out Action is Terminate.
Once I changed the Start mode to AlwaysRunning I got the correct data again. Is there anything else I should or need to change?
You do not have the required permissions to view the files attached to this post.
Everything @WillemDH suggested makes perfect sense based on what I was observing. I defer to his expertise on this particular case, but things seem functional for my application pool after applying the suggested changes.