Highlights of WCF Problems

1. The Handler "SVC-integrated" has an error module "managedpipelinehandler" in its module list"

1. HTTP 404.3-not found

   The page you requested cannot be provided due to scaling configuration issues. If the page is a script, add a handler. If you want to download the file, add the mime ing.

   Solution: run the following command as an administrator: C: \ WINDOWS \ microsoft. Net \ framework \ V3.0 \ Windows Communication Foundation \ servicemodelreg.exe-I

2. HTTP 500.21-Internal Server Error

   The handler "SVC-integrated" has an error module "managedpipelinehandler" in its module list"

   Solution:

   Cause: after the Framework v4.0 is installed, IIS is enabled again. As a result, the framework is not fully installed.

   Solution: Start-> All Programs-> attachments-> right-click and choose "command prompt"-> Run as administrator-> % WinDir % \ Microsoft. net \ framework \ v4.0.30319 \ aspnet_regiis.exe-I

   If not, check whether the IIS application pool uses the integration mode. If not, change it to the integration mode.

2. WCF add service reference gotcha with Windows Server

We recently switched from developing in Vista to Windows Server 2003. Someone had the bright idea that we shoshould develop in the same environment the application is going to be hosted on. Go figure.

What that meant is that you run into wierd issues like this one. When trying to add a service reference to a WCF Service hosted under IIS you keep getting this 'add service reference error ':

Metadata contains a reference that cannot be resolved: 'http: // Merill/services. Host/clientprofile. SVC? WSDL '.
The WSDL document contains links that cocould not be resolved.
There was an error downloading 'HTTP: // Merill/services. Host/clientprofile. SVC? XSD = xsd0 '.
The underlying connection was closed: An Unexpected error occurred on a receive.
Unable to read data from the transport connection: an existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Metadata contains a reference that cannot be resolved: 'http: // localhost/services. Host/clientprofile. svc '.
Metadata contains a reference that cannot be resolved: 'http: // localhost/services. Host/clientprofile. svc '.
If the service is defined in the current solution, try building the solution and adding the service reference again.

The key part of this message is the reference to the downloading of the XSD. When I tried accessing the. SVC URL in a browser it worked fine, but trying to access the. SVC? XSD = xsd0 brings up the generic 'could not display webpage' message.

When you unleash your weapon (Process Monitor) on the csc.exe process (this is the compiler generating the XSD) you'll realize that the IIS identity iis_wpg does not have access to the Windows \ Temp folder. give enough rights to the folder and Viola problemo solved.

Reference: http://merill.net/2008/04/wcf-add-service-reference-gotcha-with-windows-server/

3.