Event ID 5136 — 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.
|Product:||Internet Information Services|
|Message:||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.|
Stop and restart the listener adapter
Listener adapters and the Windows Process Activation Service (WAS) work closely together. If a listener adapter disconnects or cannot communicate correctly with WAS, you may have to stop and restart the listener adapter. The following example shows how to restart the HTTP listener adapter.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To restart the HTTP listener adapter:
- 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 http /y.
- At the command prompt, type net start http.
- Start any other services that were stopped when the HTTP listener adapter was shut down.
Note: This example procedure will work for listener adapters that run as a service. For listener adapters that run as a process, refer to the documentation for the program, or contact the vendor of the program for more information.
You can use an Internet browser to verify that a protocol adapter is functional by following these steps:
- Select a Web site or application that is configured to respond to the protocol you want to verify.
- In the address bar of your browser, type a protocol-specific request to the Web site or applications that you chose in step 1. For example, http://servername/default.htm
- If the protocol adapter is working, your browser client should display the expected output page.
Note: If the protocol adapter is from a third party, refer to the documentation for the adapter. The documentation may have specific steps that explain how to verify the state of the service or process that hosts the protocol adapter.