Config Wcf in dotnetnuke

                Print      Add To Favorite     Add To Watch List     Contact Author

Creator: host   8/27/2011 11:57:42 AM    Author: Michael Washington   Source: http://www.adefwebserver.com/DotNetNukeHELP/Misc/Configuring_WCF.htm   Views: 1750    0    0  
Tags:
Module develop Dnn Tutorial Dnn development dnn 6 Free Module Wcf

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


Rating People: 33   Average Rating:     
Comment List:


  No Record 


Post your comment

Your Name: Required
Your Mail: Email is used only to display Gravatar
Your Site:
CAPTCHA image
Enter the code shown above in the box below
Comment Info:         

     DnnModule.com is built to provide DNN quality modules and DNN skins, some of them are free, some not. We wish these stuffs (free or not ) can be useful to you.

     Besides that, we also provide a full range of professional services, ranging from web site build, seo, system management, administration, support, senior consultancy and security services. We act as if your development project or network was ours, with care and respect. We are not satisfied until it works the way you want it to, and we don't silently ignore found issues as somebody else's problem.