Event ID 7002 — IIS Protocol Adapter Availability
Applies To: Windows Server 2008
.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: | 7002 |
| Source: | Microsoft-Windows-WAS-ListenerAdapter |
| Version: | 7.0 |
| Symbolic Name: | WAS_LA_WAITING_TO_CONNECT_TO_WAS |
| Message: | 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. |
Resolve
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:
- Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- 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:
- 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.
- At the command prompt, type net start was.
- 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:
- Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- Type cd %Windir%\system32\inetsrv\config
- Type notepad applicationHost.config
- Find the listenerAdapters section under system.applicationHost. Make sure the protocol is entered there.
- Make sure that the protocol does not have a duplicate entry. If there is a duplicate entry, remove it.
For more information about the listenerAdapters section, see IIS 7.0: add Element for listenerAdapters (IIS Settings Schema).
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.