IIS Web Site Availability
Applies To: Windows Server 2008 R2
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.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The URL may be invalid. The site has been disabled. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The site has been disabled. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The necessary network binding may already be in use. The site has been disabled. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not configure logging for site %1. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not configure bindings for an application in site %1. The site has been disabled. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not configure logging properties for site %1. The site's log file directory path may be a mapped network path. Using a mapped network path as the site's log file directory is not supported by IIS. Use a UNC path instead. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The site's log file directory may contain an invalid computer or share name. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The server does not have permission to access the site's log file directory. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not configure the logging properties for site %1. The site's log file directory is not fully qualified, which may be because it is missing the drive letter or other important information. | |
Microsoft-Windows-IIS-W3SVC |
The virtual site %1 is invalid because the World Wide Web Publishing Service (WWW Service) could not configure valid site bindings or no site bindings exist for the site. | |
Microsoft-Windows-IIS-W3SVC |
The virtual site %1 is invalid because the application pool ID for the site is null. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service failed to enable bandwidth throttling on site '%1'. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service failed to delete the config group for the application '%1' in site '%2'. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service failed to remove the urls for the application '%1' in virtual site '%2'. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service failed to set the application pool for the application '%1' in site '%2'. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service failed to set the max connections for the virtual site '%1'. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service failed to set the connection timeout for the virtual site '%1'. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. Either the network endpoint for the site's IP address could not be created or the IP listen list for HTTP.sys did not have any usable IP addresses. The site has been disabled. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The IP address for the site is not in the HTTP.sys IP listen list. The site has been disabled. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. HTTP.sys has been configured to listen to too many ports. The site has been disabled. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not create a relationship between %1 and application %2 in site %3. The site will be stopped because the WWW Service cannot notify HTTP.sys about the application. The data field contains the error number. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) did not construct valid URLs for virtual site %1. Therefore, the virtual site %1 will be stopped. This can be caused by invalid characters in the site bindings. The following characters are not allowed in a site binding: "\"" "/" "\\" "[" "]" ":" "|" " " "<" ">" "+" "=" ";" "," "?" "*" "%" "#" "@" "{" "}" "^" "`". To fix this problem please remove invalid characters from the site bindings. | |
Microsoft-Windows-IIS-W3SVC |
The World Wide Web Publishing Service (WWW Service) failed to create binding string for site %1. Please verify that site binding (%2) is in correct format and do not contain any invalid characters. | |
Microsoft-Windows-IIS-WMSVC |
Could not initialize the logging module for site %1. The site will therefore be non-functional. | |
Microsoft-Windows-WAS |
The virtual site %1 is invalid because valid site bindings could not be configured or no site bindings exist for the site. | |
Microsoft-Windows-WAS |
Site %1 was disabled because the application pool defined for site %2 is not a valid application pool. | |
Microsoft-Windows-WAS |
Site %1 was disabled because the root application defined for the site is invalid. See the previous event log message for information about why the root application is invalid. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service failed to disassociate the application '%1' from the virtual site '%2'. The data field contains the error number. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service failed to create the application '%2' in site '%1'. The data field contains the error number. | |
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) did not create site %1. The data field contains the error number. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service failed to delete the application '%2' in site '%1'. The data field contains the error number. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service failed to delete site '%1'. The data field contains the error number. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service failed to modify the application '%2' in site '%1'. The data field contains the error number. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service failed to modify site '%1'. The data field contains the error number. | |
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) did not process changes that affect supported protocols for site %1. The site will be stopped because the system is unable to guarantee that all messages intended for the site will be processed. The data field contains the error number | |
Microsoft-Windows-WAS |
The request for protocol %1 to configure application %3 in virtual site %2 failed. The virtual site will be disabled because the protocol cannot configure the application. The data field contains the error number. | |
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) did not send a request to protocol %1 to remove configuration for application %3 in virtual site %2. WAS will assume that the protocol is disabled. To guarantee the state, start and stop the virtual site. The data field contains the error number. | |
Microsoft-Windows-WAS |
Site %1 has no root application defined, so the site will be ignored. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service recovered from a previous error creating site '%1'. See previously logged event(s). |