Event ID 2220 — IIS ISAPI Functionality

Event ID 2220 — IIS ISAPI Functionality

Updated: January 20, 2010

Applies To: Windows Server 2008

Internet Information Services (IIS) ISAPI (Internet Server Application Programming Interface) extensions and filters can extend and modify the request-processing capabilities of IIS. ISAPI filters require a long time to be written, offer no native support for session handling, and can be cumbersome to maintain. IIS 6.0 and IIS 7.0 run ISAPI applications in isolation to enhance server stability. While ISAPI filters can still be used in IIS 7.0, it is easier for developers to add managed or native modules that integrate into IIS 7.0’s new modular architecture.

Event Details

Product: Internet Information Services
ID: 2220
Source: Microsoft-Windows-IIS-WMSVC
Version: 7.0
Symbolic Name: W3_EVENT_EXTENSION_LOAD_FAILED
Message: The HTTP server was unable to load the ISAPI Application ‘%1’. The data is the error.

Resolve
Correct an ISAPI load failure

If an ISAPI Filter fails to load, possible resolutions include the following:

  • Contact the ISAPI vendor regarding the error. The vendor should have more specific knowledge about the filter’s features and behavior.
  • If the ISAPI failed to load because of a processor mismatch, see Knowledge Base article 894435.
  • Check the event log message for a specific error number included in the message. This error number will be different from the Event ID. To do this, see the steps below.

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

Check for a specific error number

To check for a specific error number:

  1. In the Event Viewer, select the event that you received.
  2. Click the Details tab, then Friendly View.
  3. If a specific error number is available, the words Binary data: should appear.
  4. Below In Words, note the number after the colon.

Find out more about a specific error number

To learn more about a specific error number:

  1. Download the Err.exe utility from the Microsoft Exchange Server Error Code Look-up page.
  2. Click Start, All Programs, Accessories, and then Command Prompt.
  3. At the command prompt, navigate to the directory where you downloaded Err.exe. For example, if you downloaded Err.exe to C:\Err, type cd C:\Err.
  4. Type err errornumber to obtain more information about the error. For example, if the specific error number is 80070005, type err 80070005.
  5. In the example described in the previous section, the error resolves to ERROR_ACCESS_DENIED, so your next step would be to check permissions on the ISAPI DLL.

Verify

You can use IIS Manager to verify that an ISAPI filter is functional by using one of the following methods:

  • Performing a test browse on the Web site or application that uses the ISAPI filter.
  • Verifying that a worker process is running for the Web site or application that uses the ISAPI filter.

Note:  An IIS worker process does not exist until a request is made to the application pool for the Web site or application. For this reason, you may have to test browse the Web site or application before you can verify that a worker process is functional.

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

Perform a test browse on the Web site or application that is using the ISAPI filter

To perform a test browse by using IIS Manager:

  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 computer name.
  4. Expand Sites.
  5. Select the Web site or application that is using the ISAPI filter that you want to verify.
  6. In the Actions pane, click the link under Browse. If the Web page appears, the ISAPI filter is functional.

Verify that an application pool worker process is running for a Web site or application

To verify that an application pool worker process is running:

  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, select the computer name.
  4. In Features View, under the Feature Name column heading, double-click the Worker Processes management feature. A list of currently active application pools and worker processes will appear.
  5. Examine the application pool corresponding to the Web site or application that uses the ISAPI filter. The State column for the worker process will indicate Running if the worker process is running.

Related Management Information

IIS ISAPI Functionality

Internet Information Services (IIS) 7.0

Related:

Event ID 2220 — Message Queuing Clustering

Event ID 2220 — Message Queuing Clustering

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Clustering makes it possible for Message Queuing to operate as one instance across multiple operating systems so that Message Queuing can fail-over from one computer to another and provide high availability.

Event Details

Product: Windows Operating System
ID: 2220
Source: MSMQ
Version: 6.1
Symbolic Name: EVENT_ERROR_MSMQ_CLUSTER_BIND_IP_NOT_EXIST
Message: <p>The IP address %1 specified in the \HKLM\Software\Microsoft\MSMQ\Parameters\%2 registry value is not a valid IP address for this computer.</p>

Resolve
Configure correct IP Address

The IP address is not configured properly in the registry.

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

To configure IP address:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

  1. Open the Registry Editor. Click Start, in the search box type regedit, and then hit ENTER.
  2. Browse to the registry key specified in the event.
  3. Either remove the registry value or set it to the IP address suggested in the event.

Verify

You can use Failover Cluster Management to determine whether the Message Queuing cluster resource is online, or you can use the Cluster.exe tool to determine whether Windows Failover Clustering is installed and running.

Related Management Information

Message Queuing Clustering

Message Queuing

Related:

A fatal MTA database server error was encountered. The Directory Entry Access Table is full. [{value}{value}{value}{value}{value}{value}{value}{value}{value}{value}{value}] (16)

Details
Product: Exchange
Event ID: 2220
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA02220
Message: A fatal MTA database server error was encountered. The Directory Entry Access Table is full. [{value}{value}{value}{value}{value}{value}{value}{value}{value}{value}{value}] (16)
   
Explanation
The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full.
   
User Action
If the Microsoft Exchange Server disk is full, delete any unnecessary files. If you suspect a disk error, run Chkdsk. Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt.If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Contact Microsoft Product Support Services for assistance.

Related:

A fatal MTA database server error was encountered. The Directory Entry Access Table is full. [ ] (16)

Details
Product: Exchange
Event ID: 2220
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: A fatal MTA database server error was encountered. The Directory Entry Access Table is full. [<value> <value> <value> <value> <value> <value> <value> <value> <value> <value> <value>] (16)
   
Explanation

The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full.

   
User Action

If the Microsoft Exchange Server disk is full, delete any unnecessary files. If you suspect a disk error, run Chkdsk.

Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Contact Microsoft Product Support Services for assistance.

Related:

A fatal MTA database server error was encountered. The Directory Entry Access Table is full. [valuevaluevaluevaluevaluevaluevaluevaluevaluevaluevalue] (16)

Details
Product: Exchange
Event ID: 2220
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: A fatal MTA database server error was encountered. The Directory Entry Access Table is full. [valuevaluevaluevaluevaluevaluevaluevaluevaluevaluevalue] (16)
   
Explanation
The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full.
   
User Action
If the Microsoft Exchange Server disk is full, delete any unnecessary files. If you suspect a disk error, run Chkdsk.

Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Contact Microsoft Product Support Services for assistance.

Related:

The group name could not be found.

Details
Product: Windows Operating System
Event ID: 2220
Source: System
Version: 5.0
Symbolic Name: NERR_GroupNotFound
Message: The group name could not be found.
   
Explanation

You specified an unknown group name.

   
User Action

Check the spelling of the group name. To display a list of the groups in the security database, type NET GROUP if you are running Windows 2000 Server. If you are running Windows 2000 Domain Controller, type NET GROUP /domain. Your Windows 2000 workstation must be a member of a domain that is running Windows 2000 Server. Otherwise, you will see a message that tells you that NET GROUP is a Windows 2000 Domain Controller command only.

Related: