| Event Id | 5159 |
| Source | Microsoft-Windows-WAS |
| Description | 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. |
| Event Information | According to Microsoft : Cause : This event is logged when Windows Process Activation Service (WAS) did not register protocol, because WAS cannot register a protocol when there are listener channels from a previous listener adapter connection for the protocol. Resolution : 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: 1.Open an elevated Command Prompt window. Click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator . 2.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: 1.Open Task Manager. Click Start, Run, type taskmgr , and press ENTER. 2.In Task Manager, click the Processes tab. 3.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. 1.Open an elevated Command Prompt window. Click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator . 2.At the command prompt, type net stop was /y . 3.At the command prompt, type net start was . 4.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: 1.Restart the process or service that hosts the listener adapter. |
| Reference Links | Event ID 5159 from Microsoft-Windows-WAS |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.