Problem with WCF web service config file--binding issue maybe?
Hello.
I am now fumbling with the new WCF stuff, and running into problems. My super-simple example web service works perfectly when I run it locally, but when I deploy to a server and try to run it, I get an error. Event log says:
WebHost failed to process a request.
Sender Information: System.ServiceModel.Servic
Exception: System.ServiceModel.Servic
This is pretty confusing since I let VS2008 create my config files. I really didn't do much with them! Does anyone know what this means and how to fix my config file(s)?
This is my system.ServiceModel section, if that helps any:
I am now fumbling with the new WCF stuff, and running into problems. My super-simple example web service works perfectly when I run it locally, but when I deploy to a server and try to run it, I get an error. Event log says:
WebHost failed to process a request.
Sender Information: System.ServiceModel.Servic
Exception: System.ServiceModel.Servic
This is pretty confusing since I let VS2008 create my config files. I really didn't do much with them! Does anyone know what this means and how to fix my config file(s)?
This is my system.ServiceModel section, if that helps any:
Last Comment
CuteBug
Could you attach your config file?
ASKER
Thanks you! This is my web.config file:
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Fra
-->
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<!--
The section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<!--
The section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
-->
<scripting>
<!--
Uncomment this section to enable the authentication service. Include
requireSSL="true" if appropriate.
-->
<!--
Uncomment these lines to enable the profile service, and to choose the
profile properties that can be retrieved and modified in ASP.NET AJAX
applications.
-->
<!--
Uncomment this section to enable the role service.
-->
<!--
<scriptResourceHandler enableCompression="true" enableCaching="true" />
-->
</scripting>
<!--
The system.webServer section is required for running ASP.NET AJAX under Internet
Information Services 7.0. It is not necessary for previous version of IIS.
-->
<!-- Service Endpoints -->
<!--
Upon deployment, the following identity element should be removed or replaced to reflect the
identity under which the deployed service runs. If removed, WCF will infer an appropriate identity
automatically.
-->
<!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
<!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->
<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Fra
-->
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<!--
The section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<!--
The section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
-->
<scripting>
<!--
Uncomment this section to enable the authentication service. Include
requireSSL="true" if appropriate.
-->
<!--
Uncomment these lines to enable the profile service, and to choose the
profile properties that can be retrieved and modified in ASP.NET AJAX
applications.
-->
<!--
Uncomment this section to enable the role service.
-->
<!--
<scriptResourceHandler enableCompression="true" enableCaching="true" />
-->
</scripting>
<!--
The system.webServer section is required for running ASP.NET AJAX under Internet
Information Services 7.0. It is not necessary for previous version of IIS.
-->
<!-- Service Endpoints -->
<!--
Upon deployment, the following identity element should be removed or replaced to reflect the
identity under which the deployed service runs. If removed, WCF will infer an appropriate identity
automatically.
-->
<!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
<!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->
ASKER
And this is the app.config on the client:
<?xml version="1.0" encoding="utf-8" ?>
<?xml version="1.0" encoding="utf-8" ?>
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Can you tell us? I'm having a similar issue...
ASKER
Wish I could. Sorry, it's been a while and I remember we tried all sorts of stuff with the config file to get it working.
I would delete the entries out of the config file and create the reference again. We did that a lot.
I would delete the entries out of the config file and create the reference again. We did that a lot.
.NET Programming
The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.
137K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
