none
BizTalk Error- The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF RRS feed

  • Question

  • Hello All,

     

    We are getting the below error while sending a response to a web service. The messages are getting suspended in the send port. We are using WCF-BasicHttp adapter. Could you please help?

     

    Error:

    System.ServiceModel.CommunicationException: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF ---> System.Net.WebException: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF

       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)

       --- End of inner exception stack trace ---

     

    Server stack trace:

       at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)

       at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)

       at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)

       at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)

     

    Exception rethrown at [0]:

       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMe

     

     

     

    Environment: BizTalk 2013 R2

    Message flow:

    External System --> BizTalk --> SAP

    SAP--> BizTalk --> External system ====> Message gets suspended at the send port in this flow

    Monday, September 23, 2019 5:36 AM

Answers

  • Looks like the error is in the response header from the web service as the error clearly states.   You will need to capture the payload, using a tool such as Fiddler, to prove that is the issue and then get the owner of the web service to fix their web service so it adheres to the protocol.
    Monday, September 23, 2019 8:15 PM

All replies

  • Looks like the error is in the response header from the web service as the error clearly states.   You will need to capture the payload, using a tool such as Fiddler, to prove that is the issue and then get the owner of the web service to fix their web service so it adheres to the protocol.
    Monday, September 23, 2019 8:15 PM
  • The owner of the web service  modified the “HTTP Response Header” value in IIS  and that fixed the issue! Thank you Colin! Your help is much appreciated!
    Tuesday, September 24, 2019 9:16 AM