Share via

MIMCM/FIMCM Troubleshooting: Portal throws IIS errors 404.2 or 404.3

  • Article

Error Description

HTTP Error 404.2 - Not Found

The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server.

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:

Module

 IsapiModule

Notification

 ExecuteRequestHandler

Handler

 ExtensionlessUrlHandler-ISAPI-4.0_64bit

Error Code

 0x800704ec

Requested URL

 https://mimcm.dev.domain.root:443/certificatemanagement

Physical Path

 C:\Program Files\Microsoft Forefront Identity Manager\2010\Certificate Management\web

Logon Method

 Negotiate

Logon User

 DEV\Administrator



More Information:

This error occurs when the necessary Web service extension is not enabled, the location or the name of the extension are misspelled or incorrectly entered.

View more information »

HTTP Error 404.3 - Not Found

The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

Most likely causes:

  •  It is possible that a handler mapping is missing. By default, the static file handler processes all content.
  •  The feature you are trying to use may not be installed.
  •  The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)
  •  If ASP.NET is not installed.

Things you can try:

  •  In system.webServer/handlers:
    •  Ensure that the expected handler for the current page is mapped.
    •  Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
    •  Pay extra attention to typographical errors in the expected handler line.
  •  Please verify that the feature you are trying to use is installed.
  •  Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.
  1.  To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']
  2.  The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
  3.  For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain']

Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them.

  • Install ASP.NET.
  •  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:

Module

 StaticFileModule

Notification

 ExecuteRequestHandler

Handler

 StaticFile

Error Code

 0x80070032

Requested URL

 https://mimcm.dev.domain.root:443/certificatemanagement/index.aspx

Physical Path

 C:\Program Files\Microsoft Forefront Identity Manager\2010\Certificate Management\web\index.aspx

Logon Method

 Negotiate

Logon User

 DEV\Administrator



More Information:

This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files.

View more information »   

Solution

Except for the solutions mentioned in the error descriptions, you can try to:

  1. Uninstall all IIS features
  2. Uninstall MIM CM
  3. Reinstall all required IIS features
  4. Reinstall MIM CM