Event ID 9001 — IIS Application Host SID Mapping Configuration

Event ID 9001 — IIS Application Host SID Mapping Configuration

Updated: March 24, 2009

Applies To: Windows Server 2008 R2

In Internet Information Services (IIS) 6.0, separate user accounts had to be created for application pools in order to isolate them. In IIS 7.0, mapped application pool SIDs (security identifiers) make this process easier. When a new Web site is created in IIS 7.0, the site receives a new application pool with the same name as the site. The Application Host Helper Service (AppHostSvc) dynamically creates a unique application pool SID based on the application pool name, and the name is mapped to the SID. Web site resources like files and directories can then be granted permissions by using the mapped application pool SID instead of separate user identities. This enables all application pools to run under the same default Network Service account, yet remain isolated.

Event Details

Product: Internet Information Services
ID: 9001
Source: Microsoft-Windows-IIS-APPHOSTSVC
Version: 7.5
Symbolic Name: APPHOSTSVC_SID_COLLISION
Message: The Application Host Helper Service encountered an error while adding the mapping for the application pool name ‘%1’ to its SID. That particular SID is already mapped to another application pool name, causing a conflict. To resolve this issue, please change the name of this application pool. The data field contains the error number.

Resolve
Change an IIS application pool name

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To change the application pool name:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections pane, expand the server node and click Application Pools.
  4. On the Application Pools page, select the application pool you want to rename.
  5. In the Actions pane, under Edit Application Pool, click Rename, type the new name in the rename text box, and then press ENTER or click outside the rename text box.

Verify

If Application Host SID Mapping is not configured correctly, Web sites in the affected application pool will fail to serve pages. For this reason, you can verify the Application Host SID Mapping functionality by performing a test browse.

To perform a test browse:

  1. Choose a Web site or an application that is configured to run in the application pool that you want to verify.
  2. Open up your default browser or required client.
  3. Browse to a page in the Web site or application that you chose in step 1.
  4. The client should display the expected output page. If Application Host SID Mapping is configured correctly, the page will be displayed.

Related Management Information

IIS Application Host SID Mapping Configuration

Internet Information Services (IIS) 7.5

Related:

Event ID 9000 — IIS Application Host SID Mapping Configuration

Event ID 9000 — IIS Application Host SID Mapping Configuration

Updated: January 20, 2010

Applies To: Windows Server 2008

In Internet Information Services (IIS) 6.0, separate user accounts had to be created for application pools in order to isolate them. In IIS 7.0, mapped application pool SIDs (security identifiers) make this process easier. When a new Web site is created in IIS 7.0, the site receives a new application pool with the same name as the site. The Application Host Helper Service (AppHostSvc) dynamically creates a unique application pool SID based on the application pool name, and the name is mapped to the SID. Web site resources like files and directories can then be granted permissions by using the mapped application pool SID instead of separate user identities. This enables all application pools to run under the same default Network Service account, yet remain isolated.

Event Details

Product: Internet Information Services
ID: 9000
Source: Microsoft-Windows-IIS-APPHOSTSVC
Version: 7.0
Symbolic Name: APPHOSTSVC_SID_CONFIG_ERROR
Message: The Application Host Helper Service encountered an error while reading the data for SID mapping. Please ensure that the application pool name data is correct in the configuration file. To resolve this issue, please recommit the changes or restart this service. The data field contains the error number.

Resolve
Reapply changes and restart AppHostSvc

When configuration changes do not appear to take effect, possible resolutions include the following:

  • Reapply the changes.
  • Reduce the number of application pools.
  • Stop and restart the Application Host Helper Service (AppHostSvc).

Stop and restart the Application Host Helper Service

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To stop and restart the Application Host Helper 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 apphostsvc.
  3. At the command prompt, type net start apphostsvc.

Verify

If Application Host SID Mapping is not configured correctly, Web sites in the affected application pool will fail to serve pages. For this reason, you can verify the Application Host SID Mapping functionality by performing a test browse.

To perform a test browse:

  1. Choose a Web site or an application that is configured to run in the application pool that you want to verify.
  2. Open up your default browser or required client.
  3. Browse to a page in the Web site or application that you chose in step 1.
  4. The client should display the expected output page. If Application Host SID Mapping is configured correctly, the page will be displayed.

Related Management Information

IIS Application Host SID Mapping Configuration

Internet Information Services (IIS) 7.0

Related:

Event ID 7006 — IIS Protocol Adapter Availability

Event ID 7006 — IIS Protocol Adapter Availability

Updated: January 20, 2010

Applies To: Windows Server 2008

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: 7006
Source: Microsoft-Windows-WAS-ListenerAdapter
Version: 7.0
Symbolic Name: WAS_LA_RECEIVED_BAD_DATA
Message: Listener Adapter protocol ‘%1’ received bad data from Windows Process Activation Service and is shutting itself down. Cause: Listener Adapter received bad data from Windows Process Activation Service. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

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:

  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.

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. For example, http://servername/default.htm
  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.

Related Management Information

IIS Protocol Adapter Availability

Internet Information Services (IIS) 7.0

Related:

Event ID 7005 — IIS Protocol Adapter Availability

Event ID 7005 — IIS Protocol Adapter Availability

Updated: January 20, 2010

Applies To: Windows Server 2008

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: 7005
Source: Microsoft-Windows-WAS-ListenerAdapter
Version: 7.0
Symbolic Name: WAS_LA_COMMUNICATION_FAILED
Message: Listener Adapter protocol ‘%1’ attempted to communicate to Windows Process Activation Service and failed. The Listener Adapter is now in a bad state. Cause: This is caused by Out of Memory issues or failures between Windows Process Activation Service and Listener Adapter. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

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:

  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.

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. For example, http://servername/default.htm
  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.

Related Management Information

IIS Protocol Adapter Availability

Internet Information Services (IIS) 7.0

Related:

Event ID 7004 — IIS Protocol Adapter Availability

Event ID 7004 — IIS Protocol Adapter Availability

Updated: January 20, 2010

Applies To: Windows Server 2008

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: 7004
Source: Microsoft-Windows-WAS-ListenerAdapter
Version: 7.0
Symbolic Name: WAS_LA_PROTOCOL_DISABLED
Message: Listener Adapter protocol ‘%1’ is unable to connect to Windows Process Activation Service because it has been disabled. Cause: Listener Adapter protocol ‘%1’ has been marked as disabled by Windows Process Activation Service due catastrophic failure. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

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:

  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.

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. For example, http://servername/default.htm
  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.

Related Management Information

IIS Protocol Adapter Availability

Internet Information Services (IIS) 7.0

Related:

Event ID 7003 — IIS Protocol Adapter Availability

Event ID 7003 — IIS Protocol Adapter Availability

Updated: January 20, 2010

Applies To: Windows Server 2008

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: 7003
Source: Microsoft-Windows-WAS-ListenerAdapter
Version: 7.0
Symbolic Name: WAS_LA_CONNECTED_TO_WAS
Message: Listener Adapter protocol ‘%1’ successfully connected to Windows Process Activation Service.

Resolve

This is a normal condition. No further action is required.

Related Management Information

IIS Protocol Adapter Availability

Internet Information Services (IIS) 7.0

Related:

Event ID 7002 — IIS Protocol Adapter Availability

Event ID 7002 — IIS Protocol Adapter Availability

Updated: January 20, 2010

Applies To: Windows Server 2008

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:

  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.

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:

  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. For example, http://servername/default.htm
  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.

Related Management Information

IIS Protocol Adapter Availability

Internet Information Services (IIS) 7.0

Related:

Event ID 5197 — IIS Worker Process Dynamic Idle

Event ID 5197 — IIS Worker Process Dynamic Idle

Updated: January 20, 2010

Applies To: Windows Server 2008

The Internet Information Services (IIS) Worker Process Activation Service (WAS) can dynamically adjust the idle time-out of worker processes based on current load. You can specify the maximum number of worker processes that can run concurrently on a Web server. If the maximum number is reached and dynamic idle is enabled, WAS dynamically reduces the idle time-out. This could allow new worker processes to start sooner and prevent the Web server from becoming unresponsive.

Event Details

Product: Internet Information Services
ID: 5197
Source: Microsoft-Windows-WAS
Version: 7.0
Symbolic Name: WAS_TURNING_OFF_DYNAMIC_IDLE_INFO
Message: The dynamic idle has been disabled in configuration. The Windows Process Activation Service (WAS) will return worker process idle timeouts to their configured settings.

Resolve

This is a normal condition. No further action is required.

Related Management Information

IIS Worker Process Dynamic Idle

Internet Information Services (IIS) 7.0

Related: