IIS Protocol Adapter Availability
Applies To: Windows Server 2008 R2
An Internet Information Services (IIS) Web server responds to requests on a given protocol by using a listener adapter. The protocol-specific listener adapter communicates with the Windows Process Activation Service (WAS) by means of a protocol adapter. If an error occurs when WAS communicates with the listener adapter through the protocol adapter, the Web server may be unable to respond to requests on the given protocol.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) was unable to register protocol %1. The listener adapter for protocol %1 may not have received information about all application pools and applications for this protocol. To resolve this issue, restart the listener adapter. The data field contains the error number. | |
Microsoft-Windows-WAS |
A worker process '%2' serving application pool '%1' failed to start a listener channel for protocol '%4' in the allotted time. The data field contains the error number. | |
Microsoft-Windows-WAS |
A worker process '%2' serving application pool '%1' failed to stop a listener channel for protocol '%4' in the allotted time. The data field contains the error number. | |
Microsoft-Windows-WAS |
A listener channel for protocol '%4' in worker process '%2' serving application pool '%1' reported a listener channel failure. The data field contains the error number. | |
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) disabled protocol %1 because WAS received bad data about the protocol. To re-enable the protocol, resolve the issue and recycle WAS. | |
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) encountered an error trying to determine the correct security identifier (SID) for the listener adapter identity for protocol %1. Because of this error, the service will not be able to allow the listener adapter to connect. To fix this, check and/or modify the identity value for this protocol in the configuration file. WAS was unable to determine the SID for the listener adapter identity for protocol %1. This error will prevent the listener adapter from connecting. | |
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) disabled protocol %1 because the protocol was unable to acknowledge a change in an application pool identity. To re-enable the protocol, resolve the issue and recycle WAS. | |
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) is disabling protocol %1 because the protocol was unable to acknowledge a change in an application pool identity. To re-enable the protocol, resolve the issue and recycle the WAS. | |
Microsoft-Windows-WAS |
A listener adapter for protocol '%4' supporting a listener channel in worker process '%2' serving application pool '%1' failed. The data field contains the error number. | |
Microsoft-Windows-WAS |
Windows Process Activation Service (WAS) did not register protocol %1, because WAS cannot register a protocol when there are listener channels from a previous listener adapter connection for the protocol. This may occur because you have worker processes running under debuggers and because orphaning may not be turned on. In this condition, WAS can detect the stop of a listener adapter, but it cannot kill the processes that contain listener channels. For this reason, WAS must wait for an admin to end these processes before a new listener adapter can connect. The data field contains the error number. | |
Microsoft-Windows-WAS |
The listener adapter serving the '%1' protocol disconnected unexpectedly. | |
Microsoft-Windows-WAS-ListenerAdapter |
Listener Adapter protocol '%1' failed to connect to Windows Process Activation Service due to identity permissions mismatch. Cause: Configured Identity for protocol '%1' in ApplicationHost.config does not match identity of process '%2' hosting Listener Adapter. Fix: Ensure that the identity for protocol '%1' is configured correctly in ApplicationHost.config. | |
Microsoft-Windows-WAS-ListenerAdapter |
Listener Adapter protocol '%1' is waiting to connect to Windows Process Activation Service. This event will only be logged once. Cause: This could be caused by either Windows Process Activation Service not being started, the protocol not being configured in <listenerAdapters> section, or another process already connected as Listener Adapter for that protocol. Fix: Ensure that Windows Process Activation Service is running, the protocol is configured in the <listenerAdapters> section, and that another process has not already connected as the Listener Adapter for that protocol. | |
Microsoft-Windows-WAS-ListenerAdapter |
Listener Adapter protocol '%1' successfully connected to Windows Process Activation Service. | |
Microsoft-Windows-WAS-ListenerAdapter |
Listener Adapter protocol '%1' is unable to connect to Windows Process Activation Service because it has been disabled. Cause: Listener Adapter protocol '%1' has been marked as disabled by Windows Process Activation Service due catastrophic failure. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter. | |
Microsoft-Windows-WAS-ListenerAdapter |
Listener Adapter protocol '%1' attempted to communicate to Windows Process Activation Service and failed. The Listener Adapter is now in a bad state. Cause: This is caused by Out of Memory issues or failures between Windows Process Activation Service and Listener Adapter. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter. | |
Microsoft-Windows-WAS-ListenerAdapter |
Listener Adapter protocol '%1' received bad data from Windows Process Activation Service and is shutting itself down. Cause: Listener Adapter received bad data from Windows Process Activation Service. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter. |