The configuration manager for WAS did not initialize Rule

  • ID:  Microsoft.Windows.InternetInformationServices.2008.The.configuration.manager.for.WAS.did.not.initialize
  • Description:   
  • Target:  IIS 7 Web Server
  • Enabled:  On Essential Monitoring

Overridable Parameters

Parameter Name Default Value Description Override
Priority 1  
Severity 2  

Run As Profiles

Name
Default

Rule Knowledgebase

Summary

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.
Causes
This rule does not contain any causes.
Resolutions

Stop and restart WAS

Stopping the WAS service will also stop the World Wide Web Publishing Service (W3SVC) if W3SVC is running. Thus, you may also have to start W3SVC.

To stop and restart WAS:

  • Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  • At the command prompt, type net stop was /y.

  • 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.
External References
This rule does not contain any external references.

See Also for Windows Internet Information Services Management Pack


Downloads for Windows Internet Information Services Management Pack

Back to top
AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED