locked
Error when calling BizTalk ESB WCF service using SOAPUI tool RRS feed

  • Question

  • Hi,

    I have an itinerary and when I call the ESB.ItineraryServices.Response.WCF service passing the message from .Net code I am able to successfully able to get a response. However when I use SOAPUI I am getting the error HTTP/1.1 400 Bad Request

    ==============Request message =====================

    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:itin="http://schemas.microsoft.biztalk.practices.esb.com/itinerary" xmlns:mic="http://microsoft.practices.esb/">
       <soap:Header>
          <itin:ItineraryDescription>
             <Name>Sample.Itinerary</Name>
             <Version>1.0</Version>
          </itin:ItineraryDescription>
       </soap:Header>
          <mic:part>
    <ns0:Add xmlns:ns0="http://tempuri.org/">
      <ns0:a>10</ns0:a>
      <ns0:b>20</ns0:b>
    </ns0:Add>
          </mic:part>
       </soap:Body>
    </soap:Envelope>

    ==============================================

    when I pass this message in SOAPUI, I get the error message

    HTTP/1.1 400 Bad Request
    Server: Microsoft-IIS/8.5
    X-Powered-By: ASP.NET
    Date: Mon, 23 Feb 2015 14:57:53 GMT
    Content-Length: 0

    Has anybody tried calling ESB Web services like ESB.ItineraryServices.Response.WCF service from SOAPUI.

    does anybody know how to fix it.

    Thanks in advance

    PLEASE HELP

    Vikram

    Monday, February 23, 2015 3:01 PM

Answers

  • The only advice to give is make sure you request you're sending from SoapUI is identical to what you are producing in the .Net client.

    They are different somehow.

    • Marked as answer by Angie Xu Tuesday, March 3, 2015 11:02 AM
    Tuesday, February 24, 2015 11:53 AM
    Moderator

All replies

  • The only advice to give is make sure you request you're sending from SoapUI is identical to what you are producing in the .Net client.

    They are different somehow.

    • Marked as answer by Angie Xu Tuesday, March 3, 2015 11:02 AM
    Tuesday, February 24, 2015 11:53 AM
    Moderator
  • Dear Vikram,

    The <soap:Body> opening tag is not present...the xml is invalid hence the bad request

    Regards,

    Mandar Dharmadhikari

    Tuesday, February 24, 2015 11:56 AM
    Moderator
  • Hi Vikarm,

    As the error says "HTTP/1.1 400 Bad Request" - This happens when the posted message doesn't match to the definition/specification of the service's request message. Ensure the message you posted matches to the one expected by the service.

    Since you have used SOPAUI after loading the service’s binding this shall be avoided.



    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

    Thursday, February 26, 2015 2:48 PM