none
Unexpected wrapper element RRS feed

  • Question

  • I’m fairly new to BizTalk and I’m testing my BizTalk application (BizTalk Server 2013 R2) for the first time.  My Orchestration is catching this General Exception:

    “An error occurred while processing the message, refer to the details section for more information

    Message ID: {0B28F34C-4FC4-4720-9877-2DDE73B39F42}

    Instance ID: {3A650FA0-1A23-4101-8557-6239024BC742}

    Error Description: System.ServiceModel.FaultException: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Unexpected wrapper element {http://schemas.xmlsoap.org/soap/envelope/}Envelope found.   Expected {http://www.multispeak.org/Version_4.1_Release}MeterRemoveNotification.</faultstring></soap:Fault></soap:Body></soap:Envelope>

       At Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)”

    The Receive Port is using the WCF-SQL Adapter.  The Send Port is using the WCF-BasicHttp adapter.

    Can you help me troubleshoot the error?

    Monday, December 19, 2016 10:09 PM

Answers

  • Hi Michael,

    You have to verify the suspended message. You can find it on the message tab of suspended orchestration.

    Looks like you are passing SOAP header and envelope both in this message directly to the orchestration, which will not work, it will not work as it contains the SOAP header and envelope.

    The XML should just contain the message content inside SOAP body. From the error looks like the webservice is expecting the message with RootNode: MeterRemoveNotification and Namespace: http://www.multispeak.org/Version_4.1_Release. Make sure you are passing the message to webservice without any extra wrapper above it.



    Rachit Sikroria (Microsoft Azure MVP)

    • Marked as answer by MichaelBeaupre Tuesday, December 20, 2016 5:13 PM
    Tuesday, December 20, 2016 3:55 AM
    Moderator

All replies

  • I forgot to mention.  I'm confident that my Endpoint Address of my Send Port is correct, because I can use this URI to view the WSDL in the browser.

    Monday, December 19, 2016 10:28 PM
  • Hi Michael,

    You have to verify the suspended message. You can find it on the message tab of suspended orchestration.

    Looks like you are passing SOAP header and envelope both in this message directly to the orchestration, which will not work, it will not work as it contains the SOAP header and envelope.

    The XML should just contain the message content inside SOAP body. From the error looks like the webservice is expecting the message with RootNode: MeterRemoveNotification and Namespace: http://www.multispeak.org/Version_4.1_Release. Make sure you are passing the message to webservice without any extra wrapper above it.



    Rachit Sikroria (Microsoft Azure MVP)

    • Marked as answer by MichaelBeaupre Tuesday, December 20, 2016 5:13 PM
    Tuesday, December 20, 2016 3:55 AM
    Moderator
  • Thank you Rachit!
    Tuesday, December 20, 2016 5:13 PM