Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.0 – Internal Server Error"

You have a Web site that is hosted on Internet Information Services (IIS) 7.0. When you visit the Web site in a Web browser, you may receive an error message that resembles one of the following:

Cause of error message 1

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. To resolve this problem, see Resolution 1.

Cause of error message 2

This problem occurs because the server that is running IIS 7.0 cannot access the configured root directory of the requested location. To resolve this problem, see Resolution 2.

Cause of error message 3

This problem occurs because the ISAPIModule module is missing from the modules list for the Web site. The ISAPIModule module is in the following location: To resolve this problem, see Resolution 3.

Cause of error message 4

This problem occurs because a script mapping is not valid. To resolve this problem, see Resolution 4.

Cause of error message 5

This problem occurs because an ISAPI filter that is not valid is loaded at the global level or at the Web site level. To resolve this problem, see Resolution 5.

Cause of error message 6

This problem occurs because an ISAPI filter that is not valid is loaded at the global level or at the Web site level. To resolve this problem, see Resolution 6.

Cause of error message 7

This problem occurs because the handler mapping for the requested resource points to a .dll file that cannot process the request. To resolve this problem, see Resolution 7.

Resolution 1

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

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Resolution 2

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

Resolution 3

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.

Resolution 4

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.

Resolution 5

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.

Resolution 6

Remove the ISAPI filter that is not valid. To do this, follow the steps in Resolution 5.

Resolution 7

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.