Click here to Skip to main content
15,886,799 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I know this is long shot but I was hoping for some guidance.

I have a WCF web service which when debugging locally works fine. As soon as I publish it to an IIS server it falls over with a message which tells me there is a SOAP error. I can connect to the services fine though a browser. I tried setting up remote debugging but it doesn't seem to be getting that far. I set up a web debugger and got this.
XML
The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.</faultstring>

I know it's nothing to do with the Web.config file because I am using WCF 4.0 simplified configuration so you don't need to set an endpoint.
I have set IncludeExceptionDetailInFaults but I am not getting anything else back. I was hoping someone else has had similar problems after publishing and can at least point me in the right direction.


****** Update ******
I have now installed IIS locally on my machine and it all works suggesting it's a permission setting on IIS or a firewall issue any idea.
Posted
Updated 23-Jan-15 0:34am
v6
Comments
Herman<T>.Instance 23-Jan-15 9:31am    
the IIS user should get the appropriate right to do it's work
Rajat_RJT 17-Feb-15 5:00am    
If its a firewall issue, then you need to write rule to allow the port which you are using.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900