Content Type text xml charset utf-8 was not supported by service

Question

I have a problem with a WCF service  I have a console application and I need to consume the service without using app config  so I had to set the endpoint  etc  by code  I do have a service reference to the svc  but I can t use the app config  Here s my code   BasicHttpBinding binding   new BasicHttpBinding     EndpointAddress address   new EndpointAddress  http   localhost 8731 WcfServicio MiServicio     MiServicioClient svc   new MiServicioClient binding  address   object ob   svc PaisesObtener      At the last line when I do svc PaisesObtener   I get the error   Content Type text xml  charset utf-8 was not supported by service http   localhost 8731 WcfServicio MiServicio   The client and service bindings may be mismatched

User · Answer

I had this error and all the configurations mentioned above were correct however I was still getting "The client and service bindings may be mismatched" error.

What resolved my error, was matching the messageEncoding attribute values in the following node of service and client config files. They were different in mine, service was Text and client Mtom. Changing service to Mtom to match client's, resolved the issue.

<configuration>
  <system.serviceModel>
      <bindings>
           <basicHttpBinding>
              <binding name="BasicHttpBinding_IMySevice" ... messageEncoding="Mtom">
              ...
              </binding>
           </basicHttpBinding>
      </bindings>
  </system.serviceModel>
</configuration>

User · Answer

I saw this problem today when trying to create a WCF service proxy  both using VS2010 and svcutil    Everything I m doing is with basicHttpBinding  so no issue with wsHttpBinding     For the first time in my recollection MSDN actually provided me with the solution  at the following link How to  Publish Metadata for a Service Using a Configuration File  The line I needed to change was inside the behavior element inside the MEX service behavior element inside my service app config file  I changed it from     amp lt serviceMetadata httpGetEnabled  true   gt    to    amp lt serviceMetadata httpGetEnabled  true  policyVersion  Policy15   gt    and like magic the error went away and I was able to create the service proxy  Note that there is a corresponding MSDN entry for using code instead of a config file  How to  Publish Metadata for a Service Using Code    Of course  Policy15 - how could I possibly have overlooked that      One more  gotcha   my service needs to expose 3 different endpoints  each supporting a different contract  For each proxy that I needed to build  I had to comment out the other 2 endpoints  otherwise svcutil would complain that it could not resolve the base URL address

User · Answer

For anyone who lands here by searching      content type  application json  charset utf-8  was not the expected type  text xml  charset utf-8   or some subset of that error   A similar error was caused in my case by building and running a service without proper attributes  I got this error message when I tried to update the service reference in my client application  It was resolved when I correctly applied  DataContract  and  DataMember  attributes to my custom classes   This would most likely be applicable if your service was set up and working and then it broke after you edited it

User · Answer

Do not forget check the bindings-related code too  So if you wrote   BasicHttpBinding binding   new BasicHttpBinding      Be sure that all your app config files contains   lt endpoint address                 binding  basicHttpBinding        not the   lt endpoint address                 binding  wsHttpBinding        or so

User · Answer

Again  I stress that namespace  svc name and contract must be correctly specified in web config file     lt service name  NAMESPACE SvcFileName  gt       lt endpoint contract  NAMESPACE IContractName    gt     lt  service gt    Example    lt service name  MyNameSpace FileService  gt   lt endpoint contract  MyNameSpace IFileService    gt   lt  service gt     Unrelevant tags ommited in these samples

User · Answer

I was facing the similar issue when using the Channel Factory  it was actually due to wrong Contract specified in the endpoint

User · Answer

In my case  I had to specify messageEncoding to Mtom in app config of the client application like that    lt  xml version  1 0  encoding  utf-8    gt   lt configuration gt       lt startup gt            lt supportedRuntime version  v4 0  sku   NETFramework Version v4 6 1    gt       lt  startup gt       lt system serviceModel gt           lt bindings gt               lt basicHttpBinding gt                   lt binding name  IntegrationServiceSoap  messageEncoding  Mtom   gt               lt  basicHttpBinding gt           lt  bindings gt           lt client gt               lt endpoint address  http   localhost 29495 IntegrationService asmx                  binding  basicHttpBinding  bindingConfiguration  IntegrationServiceSoap                  contract  IntegrationService IntegrationServiceSoap  name  IntegrationServiceSoap    gt           lt  client gt       lt  system serviceModel gt   lt  configuration gt    Both my client and server use basicHttpBinding  I hope this helps the others

User · Answer

First Google hit says       this is usually a mismatch in the client server bindings  where the message version in the service uses SOAP 1 2  which expects application soap xml  and the version in the client uses SOAP 1 1  which sends text xml   WSHttpBinding uses SOAP 1 2  BasicHttpBinding uses SOAP 1 1     It usually seems to be a wsHttpBinding on one side and a basicHttpBinding on the other

User · Answer

I was also facing the same problem recently  after struggling a couple of hours finally a solution came out by addition to   Factory  System ServiceModel Activation WebServiceHostFactory  to your SVC markup file  e g  ServiceHost Language  C   Debug  true  Service  QuiznetOnline Web UI WebServices LogService   Factory  System ServiceModel Activation WebServiceHostFactory     and now you can compile  amp  run your application successfully

User · Answer

I ve seen this behavior today when the       lt service name  A B C D  behaviorConfiguration  returnFaults  gt           lt endpoint contract  A B C ID  binding  basicHttpBinding  address     gt       lt  service gt    was missing from the web config  The service svc file was there and got served  It took a while to realize that the problem was not in the binding configuration it self

[wcf] Content Type text/xml; charset=utf-8 was not supported by service

Examples related to wcf

Examples related to endpoint