content type text/html vs. application/soap + xml

Hi all,
i'm just trying to get some WCF samples from msdn2 at work - for the time
being "TechnologySamples\Basic\Contract\Service\Duplex\CS\". After having
smoothed out some initial difficulties regarding ASP this example - beside
some others too - crashes with

The content type text/html; charset=utf-8 of the response message does not
match the content type of the binding (application/soap+xml; charset=utf-8).�}

Remark: actually the german message reads
"Der Inhaltstyp "text/html; charset=utf-8" der Antwortnachricht stimmt nicht
mit dem Inhaltstyp der Bindung (application/soap+xml; charset=utf-8) überein.
Wenn Sie einen benutzerdefinierten Encoder verwenden, sollten Sie
sicherstellen, dass die IsContentTypeSupported-Methode korrekt implementiert
ist. "

Thanks for any help
Peter

Check the binding configuration in the clients app.config and the services
web.config (or app.config for self-hosted). The <endpoint> binding should
be the same (for example: wsHttpBinding or basicHttpBinding). If bindings
are the same then check the binding configuration and ensure that the
MessageEncoding is the same.

"EnerPeter" <EnerPeter@discussions.microsoft.com> wrote in message
news:62145FC6-3FC3-41D8-AEC0-B66E71726E1D@microsoft.com...
> Hi all,
> i'm just trying to get some WCF samples from msdn2 at work - for the time
> being "TechnologySamples\Basic\Contract\Service\Duplex\CS\". After having
> smoothed out some initial difficulties regarding ASP this example - beside
> some others too - crashes with
>
> The content type text/html; charset=utf-8 of the response message does not
> match the content type of the binding (application/soap+xml;
> charset=utf-8)."}
>
> Remark: actually the german message reads
> "Der Inhaltstyp "text/html; charset=utf-8" der Antwortnachricht stimmt
> nicht
> mit dem Inhaltstyp der Bindung (application/soap+xml; charset=utf-8)
> überein.
> Wenn Sie einen benutzerdefinierten Encoder verwenden, sollten Sie
> sicherstellen, dass die IsContentTypeSupported-Methode korrekt
> implementiert
> ist. "
>
> Thanks for any help
> Peter
>
>
>

Hi,
of course i assume all these settings to be correct and really they are.
They originate from the official microsoft msdn samples. Could it be the case
that my problems result from using iis 5.1? What i'm wondering is that
already these basic samples led to so much trouble. That's really annoying
and daunting.
Peter

"Scott Holman" wrote:

> Check the binding configuration in the clients app.config and the services
> web.config (or app.config for self-hosted). The <endpoint> binding should
> be the same (for example: wsHttpBinding or basicHttpBinding). If bindings
> are the same then check the binding configuration and ensure that the
> MessageEncoding is the same.
>
> "EnerPeter" <EnerPeter@discussions.microsoft.com> wrote in message
> news:62145FC6-3FC3-41D8-AEC0-B66E71726E1D@microsoft.com...
> > Hi all,
> > i'm just trying to get some WCF samples from msdn2 at work - for the time
> > being "TechnologySamples\Basic\Contract\Service\Duplex\CS\". After having
> > smoothed out some initial difficulties regarding ASP this example - beside
> > some others too - crashes with
> >
> > The content type text/html; charset=utf-8 of the response message does not
> > match the content type of the binding (application/soap+xml;
> > charset=utf-8)."}
> >
> > Remark: actually the german message reads
> > "Der Inhaltstyp "text/html; charset=utf-8" der Antwortnachricht stimmt
> > nicht
> > mit dem Inhaltstyp der Bindung (application/soap+xml; charset=utf-8)
> > überein.
> > Wenn Sie einen benutzerdefinierten Encoder verwenden, sollten Sie
> > sicherstellen, dass die IsContentTypeSupported-Methode korrekt
> > implementiert
> > ist. "
> >
> > Thanks for any help
> > Peter
> >
> >
> >
>
>
>

I'm using IIS5.1 without issue. Post the app.config and web.config. I
assume that you installed the .net2.0 and .net3.0 on the web server. In the
IIS Manager Console is the ASP.net version for the services virtual
directory set to 2.0?

"EnerPeter" <EnerPeter@discussions.microsoft.com> wrote in message
news:F3A1F5AF-A150-415D-A30D-550964107498@microsoft.com...
> Hi,
> of course i assume all these settings to be correct and really they are.
> They originate from the official microsoft msdn samples. Could it be the
> case
> that my problems result from using iis 5.1? What i'm wondering is that
> already these basic samples led to so much trouble. That's really annoying
> and daunting.
> Peter
>
> "Scott Holman" wrote:
>
>> Check the binding configuration in the clients app.config and the
>> services
>> web.config (or app.config for self-hosted). The <endpoint> binding
>> should
>> be the same (for example: wsHttpBinding or basicHttpBinding). If
>> bindings
>> are the same then check the binding configuration and ensure that the
>> MessageEncoding is the same.
>>
>> "EnerPeter" <EnerPeter@discussions.microsoft.com> wrote in message
>> news:62145FC6-3FC3-41D8-AEC0-B66E71726E1D@microsoft.com...
>> > Hi all,
>> > i'm just trying to get some WCF samples from msdn2 at work - for the
>> > time
>> > being "TechnologySamples\Basic\Contract\Service\Duplex\CS\". After
>> > having
>> > smoothed out some initial difficulties regarding ASP this example -
>> > beside
>> > some others too - crashes with
>> >
>> > The content type text/html; charset=utf-8 of the response message does
>> > not
>> > match the content type of the binding (application/soap+xml;
>> > charset=utf-8)."}
>> >
>> > Remark: actually the german message reads
>> > "Der Inhaltstyp "text/html; charset=utf-8" der Antwortnachricht stimmt
>> > nicht
>> > mit dem Inhaltstyp der Bindung (application/soap+xml; charset=utf-8)
>> > überein.
>> > Wenn Sie einen benutzerdefinierten Encoder verwenden, sollten Sie
>> > sicherstellen, dass die IsContentTypeSupported-Methode korrekt
>> > implementiert
>> > ist. "
>> >
>> > Thanks for any help
>> > Peter
>> >
>> >
>> >
>>
>>
>>

Hi,
both framework versions - 2.0.50727 and 1.1.4322 - in ASP don't work (same
exception as noted below). I restarted IIS after witching versions.

Here's the App.config:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.serviceModel>
<client>
<endpoint name=""
address="http://localhost/servicemodelsamples/service.svc"
binding="wsDualHttpBinding"
bindingConfiguration="DuplexBinding"
contract="Microsoft.ServiceModel.Samples.ICalculatorDuplex" />
</client>
<bindings>
<!-- configure a binding that support duplex communication -->
<wsDualHttpBinding>
<binding name="DuplexBinding"
clientBaseAddress="http://localhost:8000/myClient/">
</binding>
</wsDualHttpBinding>
</bindings>
</system.serviceModel>
</configuration>

and the Web.config:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.serviceModel>
<services>
<service
name="Microsoft.ServiceModel.Samples.CalculatorService"
behaviorConfiguration="CalculatorServiceBehavior">
<!-- This endpoint is exposed at the base address provided by host:
http://localhost/servicemodelsamples/service.svc -->
<endpoint address=""
binding="wsDualHttpBinding"

contract="Microsoft.ServiceModel.Samples.ICalculatorDuplex" />
<!-- the mex endpoint is exposed at
http://localhost/servicemodelsamples/service.svc/mex -->
<endpoint address="mex"
binding="mexHttpBinding"
contract="IMetadataExchange" />
</service>
</services>
<!--For debugging purposes set the includeExceptionDetailInFaults
attribute to true-->
<behaviors>
<serviceBehaviors>
<behavior name="CalculatorServiceBehavior">
<serviceMetadata httpGetEnabled="True"/>
<serviceDebug includeExceptionDetailInFaults="False" />
</behavior>
</serviceBehaviors>
</behaviors>
</system.serviceModel>
</configuration>

They are both unchanged.



"Scott Holman" wrote:

> I'm using IIS5.1 without issue. Post the app.config and web.config. I
> assume that you installed the .net2.0 and .net3.0 on the web server. In the
> IIS Manager Console is the ASP.net version for the services virtual
> directory set to 2.0?
>
> "EnerPeter" <EnerPeter@discussions.microsoft.com> wrote in message
> news:F3A1F5AF-A150-415D-A30D-550964107498@microsoft.com...
> > Hi,
> > of course i assume all these settings to be correct and really they are.
> > They originate from the official microsoft msdn samples. Could it be the
> > case
> > that my problems result from using iis 5.1? What i'm wondering is that
> > already these basic samples led to so much trouble. That's really annoying
> > and daunting.
> > Peter
> >
> > "Scott Holman" wrote:
> >
> >> Check the binding configuration in the clients app.config and the
> >> services
> >> web.config (or app.config for self-hosted). The <endpoint> binding
> >> should
> >> be the same (for example: wsHttpBinding or basicHttpBinding). If
> >> bindings
> >> are the same then check the binding configuration and ensure that the
> >> MessageEncoding is the same.
> >>
> >> "EnerPeter" <EnerPeter@discussions.microsoft.com> wrote in message
> >> news:62145FC6-3FC3-41D8-AEC0-B66E71726E1D@microsoft.com...
> >> > Hi all,
> >> > i'm just trying to get some WCF samples from msdn2 at work - for the
> >> > time
> >> > being "TechnologySamples\Basic\Contract\Service\Duplex\CS\". After
> >> > having
> >> > smoothed out some initial difficulties regarding ASP this example -
> >> > beside
> >> > some others too - crashes with
> >> >
> >> > The content type text/html; charset=utf-8 of the response message does
> >> > not
> >> > match the content type of the binding (application/soap+xml;
> >> > charset=utf-8)."}
> >> >
> >> > Remark: actually the german message reads
> >> > "Der Inhaltstyp "text/html; charset=utf-8" der Antwortnachricht stimmt
> >> > nicht
> >> > mit dem Inhaltstyp der Bindung (application/soap+xml; charset=utf-8)
> >> > überein.
> >> > Wenn Sie einen benutzerdefinierten Encoder verwenden, sollten Sie
> >> > sicherstellen, dass die IsContentTypeSupported-Methode korrekt
> >> > implementiert
> >> > ist. "
> >> >
> >> > Thanks for any help
> >> > Peter
> >> >
> >> >
> >> >
> >>
> >>
> >>
>
>
>