| Event Id | 5136 |
| Source | Microsoft-Windows-WAS |
| Description | 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. |
| Event Information | According to Microsoft : Cause : This event is logged when Windows Process Activation Service (WAS) was unable to register protocol. Resolution : 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: 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 http /y . 3.At the command prompt, type net start http . 4.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. Verify : You can use an Internet browser to verify that a protocol adapter is functional by following these steps: 1.Select a Web site or application that is configured to respond to the protocol you want to verify. 2.In the address bar of your browser, type a protocol-specific request to the Web site or applications that you chose in step 1. 3.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. |
| Reference Links | Event ID 5136 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.