I am developing a WCF web service using .NET 3.5 with IIS7 and it works fine on my local machine. I tried publishing it on a server with IIS 6, and although I can view the WSDL in my browser, the client application does not seem to connect to it correctly. I started the application for sniffing packages (Charles Proxy), and the response to the first message is returned to the client empty (0 bytes). Each message expires after the first time.
The WCF service is part of a larger application that uses ASP.NET 3.5. This application works fine on IIS 6, so I think it is something specific for WCF. I also tried to make an exception in the SVC file to make sure it made it this far, and the exception was never thrown, so I feel that it is something lower that doesn't work.
Any thoughts? Do I need to install on an IIS5 server? If so, how can I still view WSDL in my browser?
The service is consumed through an SVC file using basicHttpBinding
Here's the meat of Web.Config (let me know if you need another part of it):
<system.net>
<defaultProxy>
<proxy usesystemdefault="False" proxyaddress="http://127.0.0.1:80" bypassonlocal="True"/>
</defaultProxy>
</system.net>
...
<system.serviceModel>
<services>
<service name="Nexternal.Service.XMLTools.VNService" behaviorConfiguration="VNServiceBehavior">
<endpoint address="" binding="basicHttpBinding" contract="Nexternal.Service.XMLTools.IVNService" />
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" name="mexHttpBinding" />
</service>
</services>
<behaviors>
<serviceBehaviors>
<behavior name="VNServiceBehavior">
<serviceMetadata httpGetEnabled="true" />
<serviceDebug includeExceptionDetailInFaults="true" />
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
</system.serviceModel>
source
share