Sunday, March 26, 2017   Login
You are here: Project » Blog  
Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"
Location: BlogsIWeb    
Posted by: Michael Washington 12/30/2007 10:07 AM

When trying to navigate to a file with the extension .svc when using II7 (that is in Windows Vista and Windows 2008), you may get an error like this:

 

Server Error in Application "Default Web Site/DotNetNuke_IWeb"

HTTP Error 404.3 - Not Found

 

Description: The page you are requesting cannot be served because of the Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web server. The page you requested has a file name extension that is not recognized, and is not allowed.

Error Code: 0x80070032

Notification: ExecuteRequestHandler

Module: StaticFileModule

Requested URL: http://localhost:80/DotNetNuke_IWeb/DesktopModules/IWebCF/CoreService.svc

Physical Path: C:\Users\Documents\Visual Studio 2005\Projects\IWeb\Website\DesktopModules\IWebCF\CoreService.svc

Logon User: Anonymous

Logon Method: Anonymous

Handler: StaticFile

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.)

What you can try:

  • In system.webServer/handlers:
  • Ensure that the expected handler for the current page is mapped.
  • Pay careful attention to preconditions (e.g. runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
  • Pay careful 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. Open a command prompt and change directory to %windir%\system32\inetsrv.
    2. To set a MIME type, use the following syntax: appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string']
    3. The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
    4. For example, to add a MIME map for a file which has the extension ".xyz", type the following at the command prompt, and then press Enter:
    5. 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.
  • 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.

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.

Server Version Information: Internet Information Services 7.0.

To resolve this:

1) Select "run" from the Start menu



2) Enter "cmd" and click OK

3) enter "cd c:\windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\" and press Enter.

4) Enter "ServiceModelReg -i" and press Enter.

5) WCF will now be installed:

 

Also see:

http://blogs.msdn.com/davidwaddleton/archive/2007/11/02/wcf-and-404-3-errors.aspx

Permalink |  Trackback

Comments (22)  
Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By anant on 6/18/2008 11:05 AM
Prefect.. worked .. thanks

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By epezhman on 7/26/2008 12:56 AM
i receive this error:

unrecoverable error : The servicemodereg toll requires both fulltrust and administrator privileges to run. you are not a local administrator for this machine.

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By admin on 7/26/2008 4:13 AM
If you receive an error that "you are not a local administrator" you must log into your computer as an administrator first.

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By http://www.aspnet35.com on 10/16/2008 7:55 AM
ping back:
http://www.aspnet35.com/Blog/post/2008/09/15/Stupid-error!-HTTP-Error-4043-Not-Found.aspx

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By jc on 10/29/2008 7:21 AM
Nice! For me there was one more step. After the service model registration a new web service extension appeared [ASP.NET v2.050727 (32-bit)] with a status of Prohibited. After I Allowed this then I was golden.

Thanks again.
jc

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Jeff on 12/1/2008 2:03 PM
Bless you.

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Jii on 12/22/2008 12:52 AM
Thanks!

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Anjan on 1/8/2009 8:38 AM
Thanks a lot

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Phillip Senn on 2/5/2009 1:52 PM
Even though I have administrator privs, I got
Unrecoverable error: The ServiceModelReg tool requires both FullTrust and Administrator privileges to run. You are not a local administrator for this machine.

So I logged out and logged in as the administrator account.
Then I uninstalled all of IIS and all of .NET 3.0 framework.

Then I reinstalled it and I think that's what fixed it.

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Mihai Marin on 2/25/2009 7:49 AM
Thank you

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Marty on 4/13/2009 5:09 PM
Your fix worked perfectly on both Windows XP and Vista Home Premium. Thank you v!!ery much for saving me more headaches from Microsoft

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Fe on 5/23/2009 8:49 AM
This solution works, thanks

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Toni on 6/1/2009 2:41 AM
I am getting the 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. I tried your fix but it didn't help in this instance. Do you have any other suggestions? Thanks

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Si on 6/20/2009 9:28 PM
Quick fix! Thanks!

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Sree on 7/15/2009 12:14 PM
One look at your description and my frustration is gone.

Thanks

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By keith on 8/4/2009 6:36 AM
worked great under win7 64-bit, thanks

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Supriya Kaluva on 9/14/2009 6:19 AM
ThankQ So much it worked

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Dave on 9/16/2009 9:48 AM
Perfect. Thanks.

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Dilli on 9/17/2009 8:40 PM
perfect work, thanks JC.

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By Gage on 11/9/2009 9:26 AM
Resolved this issue on Windows Server 08 using your solution. Excellent work, thanks for sharing.

Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By ccompton on 12/5/2009 9:41 PM
"Unrecoverable error: The ServiceModelReg tool requires both FullTrust and Administrator privileges to run. You are not a local administrator for this machine."

To fix this error run cmd as admin.
1. In the start menu right click the shortcut "Microsoft Visual Studio 2008/Visual Studio Tools>Visual Studio 2008 Command Prompt" and click run as administrator.
2. enter "cd c:\windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\" and press Enter.
3. Enter "ServiceModelReg -i" and press Enter.


Re: Configuring WCF - how to fix "HTTP Error 404.3 - Not Found"    By marat on 12/27/2009 8:33 AM
Merci pour l'article intéressant! Votre blog est devenu pour moi une sorte de manuel! Je tire de ce si grand chose de nouveau et intéressant. Merci! Bonne chance à toutes les entreprises!
jouer casino

  
Home  |  Screen Shots  |  Example Code  |  Installing  |  Download  |  Project
Copyright 2006-2009 by OpenLightGroup.net   |  Privacy Statement  |  Terms Of Use