HTTP Error 500.0 - Internal Server Error error when you open an IIS Webpage

This article helps you resolve the HTTP 500.0 error that occurs when you visit a Web site that is hosted on IIS.

Original product version:   Internet Information Services
Original KB number:   942031

Summary

This article describes HResult codes when you encounter 500.0 error on an Internet Information Services (IIS) Web application. This article is intended for Web site administrators. These errors have many causes and can affect many different system configurations. The procedures that are described in this article must be performed by a member of the administrator group on the server.

End users that experience these errors should notify the Web site administrator of the problem.

HResult code

HTTP Error 500 message indicates that a problem has occurred on the Web server that hosts the Web site at the time the error is returned.

The following is the details of these errors.

HResult code 0x80070032

Error message:

Server Error in Application "application name"
HTTP Error 500.0 - Internal Server Error
HRESULT: 0x80070032
Description of HRESULT ISAPI filter drive:\FilePath\ISAPI_FLT.dll tried to register for SF_NOTIFY_READ_RAW_DATA notification.

Cause

This problem occurs because IIS 7.0 does not support the Internet Server API (ISAPI) filter that registers for the SF_NOTIFY_READ_RAW_DATA notification.

Resolution

Do not use the ISAPI filter that registers for the SF_NOTIFY_READ_RAW_DATA notification in IIS.

HResult code 0x80070035

Error message:

Server Error in Application "application name"
HTTP Error 500.0 - Internal Server Error
HRESULT: 0x80070035
Description of HRESULT The page cannot be displayed because an internal server error has occurred.

Cause

This problem occurs because the server that is running IIS 7.0 cannot access the configured root directory of the requested location.

Resolution

Make sure that the server that is running IIS 7.0 can access the configured root directory of the requested location.

HResult code 0x8007000d

Error message:

Server Error in Application "application name"
HTTP Error 500.0 - Internal Server Error
HRESULT: 0x8007000d
Description of HRESULT Handler "ASPClassic" has a bad module "IsapiModule" in its module list.

Cause

This problem occurs because the ISAPIModule module is missing from the modules list for the Web site. The ISAPIModule module is in this location: drive:\Windows\System32\inetsrv\isapi.dll.

Resolution

Add the ISAPIModule module to the modules list for the Web site. To do this, follow these steps:

  1. Click Start, click Run, type inetmgr.exe, and then click OK.
  2. In IIS Manager, expand <server name>, expand Web sites, and then click the Web site that you want to modify.
  3. In Features view, double-click Module.
  4. In the Actions pane, click Add Native Module.
  5. In the Add Native Module dialog box, click to select the IsapiModule check box, and then click OK.

HResult code 0x800700c1

Error message:

Server Error in Application "application name"
HTTP Error 500.0 - Internal Server Error
HRESULT: 0x800700c1
Description of HRESULT The page cannot be displayed because an internal server error has occurred.

Cause

This problem occurs because a script mapping is not valid.

Resolution

Make sure that the script-mapping points to the ISAPI.dll file that can process the request. To do this, follow these steps:

  1. Click Start, click Run, type inetmgr.exe, and then click OK.
  2. In IIS Manager, expand <server name>, expand Web sites, and then click the Web site that you want to modify.
  3. In Features view, double-click Handler Mappings.
  4. Make sure that the script-mapping points to the correct ISAPI.dll file. For example, .asp files should map to the %windir%\system32\inetsrv\asp.dll file.

HResult code 0x80070005

Error message:

Server Error in Application "application name"
HTTP Error 500.0 - Internal Server Error
HRESULT: 0x80070005
Description of HRESULT LoadLibraryEx on ISAPI filter "path_of_isapi" failed.

Cause

This problem occurs because an ISAPI filter that is not valid is loaded at the global level or at the Web site level.

Resolution

Remove the ISAPI filter that is not valid. To do this, follow these steps:

  1. Click Start, click Run, type inetmgr.exe, and then click OK.
  2. In IIS Manager, expand <server name>, expand Web sites, and then click the Web site that you want to modify.
  3. In Features view, double-click ISAPI Filters.
  4. Right-click the ISAPI filter that you want to remove, and then click Remove.

HResult code 0x8007007f

There are two possibilities for HResult 0x8007007f:

  • Error message 1:

    Server Error in Application "application name"
    HTTP Error 500.0 - Internal Server Error
    HRESULT: 0x8007007f
    Description of HRESULT Calling GetProcAddress on ISAPI filter "path_of_isapi" failed.

    Cause

    This problem occurs because an ISAPI filter that is not valid is loaded at the global level or at the Web site level.

    Resolution

    To resolve the problem, remove the ISAPI filter that is not valid. To do this, follow these steps:

    1. Click Start, click Run, type inetmgr.exe, and then click OK.
    2. In IIS Manager, expand <server name>, expand Web sites, and then click the Web site that you want to modify.
    3. In Features view, double-click ISAPI Filters.
    4. Right-click the ISAPI filter that you want to remove, and then click Remove.
  • Error message 2:

    Server Error in Application "application name"
    HTTP Error 500.0 - Internal Server Error
    HRESULT: 0x8007007f
    Description of HRESULT There is a problem with the resource you are looking for, so it cannot be displayed.

    Cause

    This problem occurs because the handler mapping for the requested resource points to a .dll file that cannot process the request.

    Resolution

    To resolve the problem, edit the handler mapping for the requested resource to point to the .dll file that can process the request. To do this, follow these steps:

    1. Click Start, click Run, type inetmgr.exe, and then click OK.
    2. In IIS Manager, expand <server name>, expand Web sites, and then click the Web site that you want to modify.
    3. In Features view, double-click Handler Mappings.
    4. Right-click the script mapping that you want to edit, and then click Edit.
    5. In the Edit Script Map dialog box, type the appropriate executable file in the Executable box, and then click OK.
      For example, .asp files should map to the %windir%\system32\inetsrv\asp.dll file.

More information

For any exception thrown from the web application code, check Application event log or your own Application log, for Exception Type, Exception Message, and Exception Call Stack. If further debugging is needed, use DebugDiag latest version to capture first chance exception dumps.