Event ID 5030 — IIS WAS Availability
Applies To: Windows Server 2008 R2
The Internet Information Services (IIS) Windows Process Activation Service (WAS) is needed for most Web sites because it supports the World Wide Web Publishing Service (W3SVC), which handles HTTP requests. The WAS Process Manager maps application pools to existing worker processes and spawns new instances of W3SVC to host new application pools as needed. If WAS is not available, most Web sites will not start.
|Product:||Internet Information Services|
|Message:||Windows Process Activation Service terminated unexpectedly and the system was not configured to restart it. The Windows Process Activation Service has shut down.|
Manually restart WAS or configure it to restart automatically
Possible resolutions include the following:
- Manually restarting WAS.
- Configure WAS to restart automatically.
- Configure other actions to take when WAS fails.
- If the problem persists, attach a debugger to troubleshoot the issue, or call customer service.
To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.
Manually restart WAS
To restart WAS manually:
Note: Because the World Wide Web Publishing Service (W3SVC) depends on WAS, you may need to start W3SVC after you start WAS.
- At the command prompt, type net start was.
- To restart W3SVC, from the command prompt, type net start w3svc. Also, start any other services that were stopped when WAS was shut down.
Configure WAS to restart automatically
To configure WAS to restart automatically:
Click Start, click Control Panel, and then click Administrative Tools.
Right-click Services and select Run as administrator.
Right-click Windows Process Activation Service and select Properties.
Click the Recovery tab.
In the First failure: list, select Restart the Service.
The Recovery tab also has other actions you can specify when WAS fails. These include the following:
- Configuring WAS to automatically restart for second and/or subsequent failures
- Configuring WAS to restart after the number of minutes that you specify has elapsed
- Configuring the fail count to reset after a specified number of days
- Specifying a program to run when WAS fails and optional parameters for the program
For more information about these options, on the Recovery tab, click Help me set up recovery actions.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To verify that the WAS service is running:
- Type sc query was, and press ENTER. WAS is running if the state reported for the service is 4 RUNNING.