| Event Id | 7002 |
| Source | Microsoft-Windows-WAS-ListenerAdapter |
| Description | 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. |
| Event Information | According to Microsoft : Cause : This event is logged when Listener Adapter protocol is waiting to connect to Windows Process Activation Service. Resolution : Check the listener adapter connection to WAS Possible ways to repair a listener adapter connection to the Windows Process Activation Service (WAS) include the following: Ensure that WAS is running. Ensure that the protocol is configured in the listenerAdapters section of the ApplicationHost.config file. Ensure that another process is not already configured as a listener adapter for the protocol. To perform these procedures, you must have membership in Administrators , or you must have been delegated the appropriate authority. Ensure that the WAS service is running To ensure that the WAS service is running: 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.Type sc query was , and press ENTER. WAS is running if the state reported for the service is 4 RUNNING . Restart WAS To restart WAS: 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 . 3.At the command prompt, type net start was . 4. Start any other services that were stopped when WAS was shut down.To restart W3SVC, from the command prompt, type net start w3svc . To ensure that the protocol is configured correctly in the listenerAdapters section: 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.Type cd %Windir%\system32\inetsrv\config 3.Type notepad applicationHost.config 4.Find the listenerAdapters section under system.applicationHost . Make sure the protocol is entered there. 5.Make sure that the protocol does not have a duplicate entry. If there is a duplicate entry, remove it. 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 7002 from Microsoft-Windows-WAS-ListenerAdapter |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.