Event ID 5159 — IIS Protocol Adapter Availability
Applies To: Windows Server 2008 R2
.jpg)
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.
Event Details
| Product: | Internet Information Services |
| ID: | 5159 |
| Source: | Microsoft-Windows-WAS |
| Version: | 7.5 |
| Symbolic Name: | WAS_ATTEMPT_TO_REGISTER_PROTOCOL_WITH_RQI |
| Message: | 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. |
Resolve
Stop the listener adapter and restart WAS
Listener adapters and the Windows Process Activation Service (WAS) work closely together. If a listener adapter experiences catastrophic failure, you will have to end the listener adapter process or service, stop and restart WAS, and then restart the listener. To recover from a failed listener adapter, follow these steps.
To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.
Note: In order to prevent exiting code routines from running, it is better to stop a listener adapter service first before trying to end a listener adapter process.
Stop a listener adapter service
To stop a listener adapter service:
- 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 servicename /y where servicename is the name of the listener adapter service.
End a listener adapter process
To end a listener adapter process:
- Open Task Manager. Click Start, Run, type taskmgr, and press ENTER.
- In Task Manager, click the Processes tab.
- Select the listener adapter process and click End Process.
Stop and restart WAS
To stop and restart WAS:
Stopping the WAS service will also stop the World Wide Web Publishing Service (W3SVC) and any other services that depend on WAS. Thus, you may also have to restart these other services.
- 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.
Restart the listener adapter
To restart the listener adapter:
- Restart the process or service that hosts the listener adapter.
Verify
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, https://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.