Configuration request for web site failed

Microsoft.Windows.InternetInformationServices.10.0.WebSite.WAS.Failed.To.Process.ConfigurationRequest.For.WebSite.Monitor (UnitMonitor)

Knowledge Base article:

Summary

Internet Information Services (IIS) Web sites that use HTTP rely on several important IIS components for their availability. The Windows Process Activation Service (WAS), the World Wide Publishing Service (W3SVC), the HTTP service, all must be running correctly. In addition, a properly running application pool must be available for the Web site’s applications. If any of these components is not functioning, the Web site will not be available.

Resolutions

Stop and restart the site

On startup, WAS reads information from the ApplicationHost.config file. Part of the information that WAS reads is application configuration, such as enabled protocols and the application pools for the application. For applications to be configured correctly, there must be clear communication between WAS and the protocol for the application. Stopping and starting a site can reestablish this communication.

To stop and restart the site:

You can also do this using the links below:

Stop Web Site

Start Web Site

Element properties:

TargetMicrosoft.Windows.InternetInformationServices.10.0.WebSite
Parent MonitorSystem.Health.ConfigurationState
CategoryConfigurationHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.InternetInformationServices.10.0.WebSite.EventLogManualReset2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Configuration request for web site failed
{0}
RunAsDefault