ISAPI application error detected

Summary

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 run ISAPI applications in isolation to enhance server stability. While ISAPI filters can still be used in IIS 7, it is easier for developers to add managed or native modules that integrate into IIS 7’s new modular architecture..

Resolutions

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.

Check for a specific error number

To check for a specific error number:

• In the Event Viewer, select the event that you received.

• Click the Details tab, then Friendly View.

• If a specific error number is available, the words Binary data: should appear.

• 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:

• Download the Err.exe utility from the Microsoft Exchange Server Error Code Look-up page.

• Click Start, All Programs, Accessories, and then Command Prompt.

• 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.

• Type err errornumber to obtain more information about the error. For example, if the specific error number is 80070005, type err 80070005.

• 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.