This monitor checks the status of the IIS Application Pool. If you receive an alert from this monitor, action is required in order to bring the Application Pool back to an operational state.
An IIS Application Pool site can be either in a "Started" or "Stopped" operational state.
An IIS Application Pool can stop for many reasons, including:
The Application Pool was stopped by an administrator
The Application Pool was improperly configured which caused it to fail or prevented it from starting.
If an IIS Application Pool is stopped you can diagnose the issue or restart the Application Pool by taking the following actions:
Check for additional Application Pool related alerts that might have occurred concurrently. These alerts might help better identify the reason why the service entered a stopped state.
Review the event logs on the managed computer, and correct any underlying problems that might have caused the Application Pool to stop unexpectedly.