This could be due to the service endpoint binding not using the HTTP protocol

Question

I have a WCF Service running fine on my local machine  I put it on the servers  and I am receiving the following error      An error occurred while receiving the   HTTP response to   http   xx xx x xx 8200 Services WCFClient svc    This could be due to the service   endpoint binding not using the HTTP   protocol  This could also be due to an   HTTP request context being aborted by   the server  possibly due to the   service shutting down   See server   logs for more details     I have gone to the service in the url and it is working correctly  All I am doing for the function is returning a string to an image name  so the data being passed isn t a lot  I have traced the log and it gives me the same information  Here is my client config    lt binding name  basicHttpBinding IWCFClient  closeTimeout  00 01 00           openTimeout  00 01 00  receiveTimeout  00 10 00  sendTimeout  00 01 00           bypassProxyOnLocal  false  hostNameComparisonMode  StrongWildcard           maxBufferPoolSize  2147483647  maxReceivedMessageSize  2147483647           messageEncoding  Text  textEncoding  utf-8  useDefaultWebProxy  true           allowCookies  false  gt       lt readerQuotas maxDepth  2147483647  maxStringContentLength  2147483647                     maxArrayLength  2147483647  maxBytesPerRead  2147483647                     maxNameTableCharCount  2147483647    gt       lt security mode  None  gt           lt transport clientCredentialType  None  proxyCredentialType  None  realm      gt           lt message clientCredentialType  UserName  algorithmSuite  Default    gt       lt  security gt   lt  binding gt   lt endpoint name  basicHttpBinding IWCFClient       address  http   localhost 4295 Services WCFClient svc      binding  basicHttpBinding       bindingConfiguration  basicHttpBinding IWCFClient       behaviorConfiguration  WCFGraphicManagementTool Services ClientBehavior      contract  WCFClient IWCFClient    gt    Here is my server config    lt service behaviorConfiguration  WCFGraphicManagementTool Services WCFClientBehavior      name  WCFGraphicManagementTool Services WCFClient  gt      lt endpoint name  basicHttpBinding IWCFClient         address            binding  basicHttpBinding          contract  WCFGraphicManagementTool Contracts IWCFClient    gt      lt endpoint         address  mex          binding  mexHttpBinding          contract  IMetadataExchange    gt   lt  service gt   lt behavior name  WCFGraphicManagementTool Services WCFClientBehavior  gt      lt dataContractSerializer maxItemsInObjectGraph  2147483647    gt      lt serviceThrottling maxConcurrentCalls  120  maxConcurrentSessions  120                        maxConcurrentInstances  120    gt      lt serviceMetadata httpGetEnabled  true    gt      lt serviceDebug includeExceptionDetailInFaults  true    gt   lt  behavior gt    Would it be a setting on the server since it works on my local machine

User · Answer

This error can be because of contract mismatch. Consider the three layered application below...

UI Layer
|
Process Layer
|
Data Access Layer
-> Contract Between Process and UI layer has the same enum with missing (Onhold = 3). Enum: Start = 1, Stop = 2. -> Contract Between Data Access And Process layer has enum Enum: Start = 1,Stop = 2,Onhold = 3.

In this case we will get the same error in process layer response.

The same error comes in other contract mismatch in multilayered application.

User · Answer

I was facing the same issue and solved with below code   if any TLS connectivity issue   System Net ServicePointManager SecurityProtocol   SecurityProtocolType Tls12   SecurityProtocolType Tls11   SecurityProtocolType Tls    Please paste this line before open the client channel

User · Answer

If you have a database working in visual studio   make sure there are no foreign keys in the tables  I had foreign keys and it gave me this error and when I removed them it ran smoothly

User · Answer

My problem was too many items were being passed between client and server  I had to change this settings in the behavior on both sides    lt dataContractSerializer maxItemsInObjectGraph  2147483646   gt

User · Answer

in my case   my service has function to download Files  and this error only shown up on trying to download Big Files   so I found this answer to Increase maxRequestLength to needed value in web config   I know that s weird  but problem solved  if you don t make any upload or download operations maybe this answer will not help you

User · Answer

For more insight into this issue  also see   An existing connection was forcibly closed by the remote host - WCF  My problem ended up being that my data transfer objects were too complex  Start withsimple properties like public long Id   get  set    and once you get that working than start adding additional stuff as needed

User · Answer

This could be due to many reasons  below are few of those    If you are using complex data contract objects that means custom object with more child custom objects   make sure you have all the custom objects decorated with DataContract and DataMember attributes If your data contract objects use inheritance  make sure all base classes has the DataContract and DataMember attributes  Also  you need to have the base classes specify the derived classes with the  KnownType typeof BaseClassType    attribute   check out more info here on this   Make sure all your data contract object properties have both get and set properties

User · Answer

Also had this issue and it was due to forgetting to decorate my model with DataContract and DataMember attributes

User · Answer

I think the best way to solve this is to follow the error advice  hence looking for server logs  To enable logs I added     lt system diagnostics gt       lt sources gt         lt source name  System ServiceModel  switchValue  Information  ActivityTracing  propagateActivity  true  gt           lt listeners gt             lt add name  traceListener  type  System Diagnostics XmlWriterTraceListener  initializeData  c  logs TracesServ ce svclog    gt           lt  listeners gt         lt  source gt       lt  sources gt     lt  system diagnostics gt    Then you go to c  logs TracesServ ce svclog open it with microsoft service trace viewer  And see what the problem really is

User · Answer

In my instance  the error was generated because one of my complex types had a property with no set method   The serializer threw an exception because of that fact  Added internal set methods and it all worked fine   Best way to find out why this is happening  in my opinion  is to enable trace logging   I achieved this by adding the following section to my web config    lt system diagnostics gt     lt sources gt       lt source name  System ServiceModel MessageLogging  switchValue  Warning ActivityTracing  gt         lt listeners gt           lt add name  traceListener                type  System Diagnostics XmlWriterTraceListener                initializeData   c  log Traces svclog    gt           lt add type  System Diagnostics DefaultTraceListener  name  Default    gt         lt  listeners gt       lt  source gt       lt source propagateActivity  true  name  System ServiceModel  switchValue  Verbose ActivityTracing  gt         lt listeners gt           lt add name  traceListener                type  System Diagnostics XmlWriterTraceListener                initializeData   c  log Traces svclog    gt           lt add type  System Diagnostics DefaultTraceListener  name  Default    gt         lt  listeners gt       lt  source gt     lt  sources gt     lt trace autoflush  true    gt   lt  system diagnostics gt    Once set  I ran my client  got exception and checked the  Traces svclog  file  From there  I only needed to find the exception

User · Answer

For me the solutions of this Error very strange  It was the issue of port address of EndpointAddress  In Visual studio port address of your file  e g  Service1 svc  and port address of your wcf project must be the same which you gives into EndpointAddress  Let me describe you this solution in detail   There are two steps to check the port addresses    In your WCF Project right click to your Service file  e g  Service1 svc  -  than select View in browser now in your browser you have url like http   localhost 61122 Service1 svc   so now note down your port address as a 61122  Righ click your wcf project -  than select Properties -  go to the Web Tab -  Now in Servers section -  select Use Visual Studio Development Server -  select Specific Port and give the port address which we have earlier find from our Service1 svc service  That is  61122     Earlier I have different port address  After Specifying port address properly which I have given into EndpointAddress  my problem was solved    I hope this might be solved your issue

User · Answer

Solution with DataContract  Flags for Enums looks a bit ugly  In my case problem been solved by adding something like  NotSet   0  into enum   public enum Fruits     UNKNOWN   0    APPLE   1    BALL   2    ORANGE   3

User · Answer

I struggled with this for a couple of days and tried every answer from this post and many others and share my solution because symptoms were the same but the problem was different   The problem was that the app pool was configured with a memory limit and it just get recycled after a variable period of time   Hope this helps somebody else  Greetings

User · Answer

I had this problem  This could be due to the service endpoint binding not using the HTTP protocol  and the WCF service would shut down  in a development machine   I figured out  in my case  the problem was because of Enums    I solved using this       DataContract       Flags      public enum Fruits                EnumMember          APPLE   1           EnumMember          BALL   2           EnumMember          ORANGE   3           I had to decorate my Enums with DataContract  Flags and all each of the enum member with EnumMember attributes   I solved this after looking at this msdn Reference

User · Answer

I had this problem because I configured my WCF Service to return a System Data DataTable   It worked fine in my test HTML page  but blew up when I put this in my Windows Form application   I had to go in and change the Service s Operational Contract signature from DataTable to DataSet and return the data accordingly   If you have this problem  you may want to add an additional Operational Contract to your Service so you do not have to worry about breaking code that rely on existing Services

User · Answer

To fix this  we had to changed the AppPool Identity to an administrator account

User · Answer

I ve had this same error and the problem was serialization  I managed to find the real problem using Service Trace Viewer http   msdn microsoft com en-us library ms732023 aspx and solved it easy   Maybe this will help someone

User · Answer

My problem was  that return type of my service was string  But I returned string of type xml    lt reponse gt  lt state gt 1 lt  state gt  lt message gt Operation was successfull lt  message lt  response gt    so error was thrown

User · Answer

I figured out the problem  It ended up being a path to my config file was wrong  The errors for WCF are so helpful sometimes

User · Answer

This might not be relevant to your specific problem  but the error message you mentioned has many causes  one of them is using a return type for an  OperationContract  that is either abstract  interface  or not known to the WCF client code   Check the post  and solution  below  https   stackoverflow com a 5310951 74138

User · Answer

I think there is serialization problem  you can find exact error just need to add below code in service config in  lt configuration gt  section  After config update  quot App tracelog svclog quot  file will create  where your service exist just need to open  svclog file and find red color line on left side panel which is error and see its description for more info  I hope this will help to find your error   lt configuration gt            lt system diagnostics gt       lt sources gt         lt source name  quot System ServiceModel MessageLogging quot  switchValue  quot Warning  ActivityTracing quot  gt           lt listeners gt             lt add name  quot ServiceModelTraceListener quot    gt           lt  listeners gt         lt  source gt         lt source name  quot System ServiceModel quot  switchValue  quot Verbose ActivityTracing quot  gt           lt listeners gt             lt add name  quot ServiceModelTraceListener quot    gt           lt  listeners gt         lt  source gt         lt source name  quot System Runtime Serialization quot  switchValue  quot Verbose ActivityTracing quot  gt           lt listeners gt             lt add name  quot ServiceModelTraceListener quot    gt           lt  listeners gt         lt  source gt       lt  sources gt       lt sharedListeners gt         lt add initializeData  quot App tracelog svclog quot  type  quot System Diagnostics XmlWriterTraceListener  System  Version 2 0 0 0  Culture neutral  PublicKeyToken b77a5c561934e089 quot  name  quot ServiceModelTraceListener quot  traceOutputOptions  quot Timestamp quot    gt       lt  sharedListeners gt     lt  system diagnostics gt      lt  configuration gt   Update  If you will not able to find updated  quot App tracelog svclog quot  file then please find  quot  lt some GUID gt App tracelog svclog quot  like  quot a39e3026-5dd8-4d39-842a-04d486615eedApp tracelog svclog quot

User · Answer

I ve seen this error caused by a circular reference in the object graph  Including a pointer to the parent object from a child will cause the serializer to loop  and ultimately exceed the maximum message size

[wcf] This could be due to the service endpoint binding not using the HTTP protocol

Examples related to wcf

Examples related to exception-handling

Examples related to wcf-binding

Examples related to net.tcp

Examples related to wcf-endpoint