This monitor checks the status of the Windows Process Activation service (WAS). If you receive an alert from this monitor, action is required in order to bring the service back to an operational state.
Windows Process Activation Service (WAS) manages application pool configuration and the creation and lifetime of worker processes for HTTP and other protocols. The World Wide Web Publishing Service (W3SVC) and other services depend on WAS.
Operational States:
The Windows Process Activation service (WAS) can be either in a "Service Running" or "Service Not Running" operational state.
A service can stop for many reasons, including:
The service was stopped by an administrator.
The service was prevented from starting because the user account could not be authenticated.
The service encountered an exception that stopped the service.
The service was improperly configured, which prevented it from starting.
If the Windows Process Activation service (WAS) is not running you can diagnose the issue or restart the service by taking the following actions:
Check for additional service-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 service to stop unexpectedly.
Use the following Task to attempt to restart the service.
Because the World Wide Web Publishing Service depends on the Windows Process Activation service you might need to start it as well.
Start Windows Process Activation service (WAS) Service
Start Web Server (W3SVC) Service
