Tag: Event 7006

Event ID 7006 — IIS Protocol Adapter Availability

PCIS Support Team Leave a comment

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 7006 — Basic Service Control Manager Operations

PCIS Support Team Leave a comment

Event ID 7006 — Basic Service Control Manager Operations

Updated: December 11, 2007

Applies To: Windows Server 2008

The basic operations that Service Control Manager (SCM) performs include managing the services and driver services that allow the operating system to start successfully, and reporting when one of these services or driver services fail during system startup. These operations are not associated with any particular service.

Event Details

Product: Windows Operating System
ID: 7006
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_CALL_TO_FUNCTION_FAILED_II
Message: The %1 call failed for %2 with the following error: %3

Resolve
Review the event log messages

To resolve this issue, review the Event logs and note if any other events have been logged by the Service Control Manager (SCM) Eventlog Provider. The event log message and related events logged by the SCM should help you to further troubleshoot and resolve the issue. Some examples are provided below.

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

  1. If event ID 7011 is also logged for a service, then extending the service timeout period to resolve event ID 7011 would also resolve this error.
  2. If event ID 7034 is also logged for a service, then restoring the service default settings to resolve event ID 7034 would also resolve this error.

If the issue remains unresolved, contact Microsoft support and provide the error information. For information about how to contact Microsoft support, see Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=89446).

To review the events logged by the SCM:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.

Verify

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

To verify that the Service Control Manager (SCM) is successfully sending commands to services:

  1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Right-click on a stopped service that is not a system service and select Start. If the SCM was successful in starting the service, the Status field for that service will display Started.

 To verify that the Service Control Manager is logging service events correctly:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.
  4. Review the events and confirm that event ID 7036 was logged for the action taken by the SCM in step 1 of the To verify that the Service Control Manager is successsfully sending commands to services procedure above.

Related Management Information

Basic Service Control Manager Operations

Core Operating System

Related:

The %1 call failed for %2 with the following error: %3

PCIS Support Team Leave a comment
Details
Product: Windows Operating System
Event ID: 7006
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_CALL_TO_FUNCTION_FAILED_II
Message: The %1 call failed for %2 with the following error: %3
   
Explanation

The service controller could not set a registry entry’s value for a function that it requires for operation.
   
User Action

Contact your technical support group.

Related:

This application uses too many XSL transforms.

PCIS Support Team Leave a comment
Details
Product: SQL Server Notification Services
Event ID: 7006
Source: NotificationServices
Version: 2.0.9999.9
Message: This application uses too many XSL transforms.
   
Explanation
This error occurs when the number of XSL transforms defined in your ADF is exceedingly high.

For efficiency, the XsltFormatter class keeps a cache of all XSLT transform files that it uses. This cache has a maximum limit, which is set at 1000. If your ADF defines more than 1000 XSLT files to be used for content formatting, and if at least one distributor happens to use more than 1000 of these XSLT files, then the distributor logs error 7006.
   
User Action
Reduce the number of XSLT files used in your ADF. There are several ways you can do this. Here are a few suggestions:

Consolidate XSLT files. You can have one XSLT file that formats notifications differently based on whatever logic you deem appropriate.

Use another kind of content formatter.

If your instance contains many applications, consider separating them into multiple Notification Services instances.

Related: