WCF is deployed under IIS with an error as follows:
Server error in Application "DEFAULT WEB SITE/IMF"
Internet Information Services 7.0
Error summary
HTTP error 404.3-not found the page you requested is not available due to an extended configuration issue. If the page is a script, add a handler. If you should download the file, add a MIME map.
Detailed error Information staticfilemoduleexecuterequesthandlerstaticfile0x80070032http://localhost:80/imf/metadataservice.svce:\ Development\imf\deploy\services\metadataservice.svc Anonymous Anonymous
The most probable cause:
The handler mappings may be missing. By default, the static file handler processes all content. The feature you are using may not be installed. No corresponding MIME mappings are enabled for the Web site or application. (Warning: Please do not download for users.) Create MIME mappings for content such as ASPX pages or. config files. ) If you do not install ASP.
Actions you can try:
In System.webserver/handlers: Ensure that the handlers required for the current page are mapped. Please pay special attention to the premises (for example, RuntimeVersion, Pipelinemode, bitness) and compare these prerequisites to the settings of the application pool. Pay particular attention to the writing errors in the desired handler line. Make sure the feature you want to use is already installed. Verify that MIME mappings are enabled, or use the command-line tool Appcmd.exe to add MIME mappings for your Web site. To set the MIME type, use the following syntax:%systemroot%\windows\system32\inetsrv\appcmd set config/section:staticcontent/+[fileextension= ' String ', mimetype= ' string '] variable fileextension string is the file extension, and the variable MimeType string is a file type description. For example, to add a MIME map for a file with an extension of ". XYZ": Appcmd set Config/section:staticcontent/+[fileextension= '. xyz ', mimetype= ' Text/plain ']
Warning: Please confirm that your WEB server requires this MIME mapping before adding it to the list. Configuration files, such as. CONFIG) or a dynamic script page, such as. ASP or. ASPX) should not be downloaded directly, and should always be handled through handlers. Sometimes other files are used, such as database files or. XML or. MDF, for storing configuration files) to store configuration information. Verify that the client can download these types of files before you enable them.
Install ASP. Create a trace rule to track failed requests for this HTTP status code. For more information about creating a trace rule for a failed request, click here.
Links and more information This error occurs when the file name extension of the requested URL is for a MIME type that is not configured on the server. You can add MIME types to file extensions for files other than dynamic script pages, databases, or configuration files. These file types are handled using a handler. You should not allow direct download of dynamic script pages, databases, or configuration files.
Workaround: Run the command as administrator: C:\Windows\Microsoft.NET\Framework\v3.0\Windows communication foundation\servicemodelreg.exe-i
It is important to note that if you install. NET Framework3.5 After you install IIS, the registration will fail.
Transferred from: http://hi.baidu.com/luyanvv/item/6f04901c4892aef286ad4e29
IIS7.0 deploying WCF 404 or Configuring MIME (GO)