Most likely causes:

• No handler mapping for this request was found. A feature may have to be installed.
• The Web service extension for the requested resource is not enabled on the server.
• The mapping for the extension points to the incorrect location.
• The extension was misspelled in the browser or the Web server.

Things you can try:

• Install the feature that handles this request. For example, if you get this error for an .ASPX page, you may have to install ASP.NET via IIS setup.
• Verify that the Web service extension requested is enabled on the server.
  1. Open the IIS Manager and navigate to the server level.
  2. In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed.
  3. If the extension is not in the list, click Add in the Actions pane.
  4. In the Add ISAPI and CGI Restrictions dialog box, type the path of the .dll or .exe file in the ISAPI or CGI Path box, or click Browse to navigate to the location of the file.
  5. In the Description box, type a brief description of the restriction.
  6. (Optional) Check "Allow extension path to execute" to allow the restriction to run automatically. If you do not check this option, the restriction status is Not Allowed, which is the default. You can allow the restriction later by selecting it and clicking Allow on the Actions pane.
  7. Click OK.
  NOTE: Make sure that this Web service extension or CGI is needed for your Web server before adding it to the list.
• Verify that the location of the extension is correct.
• Verify that the URL for the extension is spelled correctly both in the browser and the Web server.
• Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

Detailed Error Information:

More Information:

View more information »