none
Issue in Consuming Web Service from BizTalk RRS feed

  • Question

  • Dear Experts,

    I am facing Issue in Consuming Web Service from BizTalk:

    below error is shown up.

    Orchestration suspend due to following exception :
     An error occurred while processing the message, refer to the details section for more information
    Message ID: {4AE4748A-9F17-4841-BD94-EA3671DF8DC0}
    Instance ID: {FA5E8AAD-FE02-4A57-8B96-20608F77C336}
    Error Description: There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML assembler" Send Port: "WarrantySendPort" URI: "http://Temp/Details/AddWarranty?wsdl" Reason: The document type "http://XSD.Bank/V1#ADD__WARRANTY" does not match any of the given schemas. 

    Tuesday, June 2, 2015 10:27 AM

Answers

  • I take it then that you issue with Web Services is resolved? If so then close this thread and start a fresh thread with your other issues. This helps the group to better collaborate.

    moving BizTalk databases from one server to another is what you've not properly done. Refer https://msdn.microsoft.com/en-us/library/aa559835.aspx for steps on how to do that.

    Regards.

    • Marked as answer by Angie Xu Friday, June 19, 2015 2:16 AM
    Thursday, June 4, 2015 4:25 AM
  • Shankycheil,

    This is my very first experience to work in BizTalk.

    I got it, as it was wrong with multi-part messages.

    Now I have another issue, here we have 2 database servers with same data, when I switched the database BizTalk is not picking the data.

    Please advise.

    Regards,

    • Marked as answer by Angie Xu Friday, June 19, 2015 2:16 AM
    Wednesday, June 3, 2015 2:19 PM

All replies

  • Hi,

    I believe the most simpler way to fix this issue is to change the Send Pipeline used, by a PassThru Transmit.

    If you really need to use a XMLTransmit one, you will have to add the specified Schema to the XMLAssembler component definition of the pipeline.

    Regards.


    When an answer is helpful, please vote as helpful, propose as answer and/or mark as answer



    • Edited by ohawari Tuesday, June 2, 2015 11:07 AM
    Tuesday, June 2, 2015 11:04 AM
  • Your send port configuration is incorrect. You have also included the ?WSDL as part of the URI.

    Regards.

    Tuesday, June 2, 2015 11:10 AM
  • Thanks for the quick reply, I will test what you advised
    Tuesday, June 2, 2015 11:22 AM
  • Thanks for quick reply

    yes in included ?WSDL in it.

    Is it causing the problem ?

    Tuesday, June 2, 2015 11:23 AM
  • I am already using  "DocumentSpecNames" but its not working for me :(
    Tuesday, June 2, 2015 11:25 AM
  • After removing ?WSDL from URL the error is still there :(
    Tuesday, June 2, 2015 11:26 AM
  • If you are only sending the request to the web service, I recommend to use the Passthru Transmit Pipeline instead of a XMLTransmit one. Have you tried doing this change?

    Apart of that, how are you setting the schema in the DocumentSpecNames? You have to set the full qualified name of the schema. Also check that the schema you are setting is the the correct one and matches the namespace http://XSD.Bank/V1 and root node ADD__WARRANTY

    Regards.


    When an answer is helpful, please vote as helpful, propose as answer and/or mark as answer

    Tuesday, June 2, 2015 11:31 AM
  • Dear ohawari,

    Actually I am new in BizTalk and its my first task I am working on it.

    I am adding DocumentSpecNames with full qualified name of schema.

    Actually in the schema there are 3 elements.

    1. ADD_WARRANTY

    2 LOGIN

    Third one is the results(Response) of web service.

    Here in DocumentSpecNames I am assigning part of LOGIN.

    Please advise

    Warm Regards,

    Tuesday, June 2, 2015 11:43 AM
  • ohawari can you please share your email id so that I may send you wsdl etc for the verification
    Tuesday, June 2, 2015 11:44 AM
  • Did you use the "Add Generated Items" - Consume MEX endpoint to generate the schemas, client orchestration and bindings file for consuming this Web Service?

    Did you deploy the Web Service schemas in BizTalk?

    You are getting this error because BizTalk cannot find a schema of type "http://XSD.Bank/V1#ADD__WARRANTY" in your BizTalk configuration. Can you check against the published schemas for this ?

    Regards.

    Tuesday, June 2, 2015 1:00 PM
  • Shankycheil,

    I have only WSDL I added it as web reference, it has generated the reference.xsd that contains "http://XSD.Bank/V1#ADD__WARRANTY".

    Regards,

    Tuesday, June 2, 2015 1:26 PM
  • You can use the wizard to generate all the required elements (schemas, port types, message types, etc.) by consuming the WSDL (online or offline as WSDL file). Refer https://msdn.microsoft.com/en-us/library/bb226552.aspx on how to do that. Notice the option to use the WSDL file instead of the active endpoint.

    When you do this, it will create the XSD pertaining to the messages. When you publish these XSD into BizTalk, the schemas will be available and the XML Pipeline will not complain anymore.

    Regards.

    Wednesday, June 3, 2015 5:16 AM
  • Thanks Shankycheil,

    Let me try this one.

    Actually I added the WSDL offline with file.

    I will share my findings shortly.

    Regards,

    Wednesday, June 3, 2015 6:11 AM
  • Shankycheil,

    This is my very first experience to work in BizTalk.

    I got it, as it was wrong with multi-part messages.

    Now I have another issue, here we have 2 database servers with same data, when I switched the database BizTalk is not picking the data.

    Please advise.

    Regards,

    • Marked as answer by Angie Xu Friday, June 19, 2015 2:16 AM
    Wednesday, June 3, 2015 2:19 PM
  • I take it then that you issue with Web Services is resolved? If so then close this thread and start a fresh thread with your other issues. This helps the group to better collaborate.

    moving BizTalk databases from one server to another is what you've not properly done. Refer https://msdn.microsoft.com/en-us/library/aa559835.aspx for steps on how to do that.

    Regards.

    • Marked as answer by Angie Xu Friday, June 19, 2015 2:16 AM
    Thursday, June 4, 2015 4:25 AM
  • Thanks Shankycheil

    Regards

    Thursday, June 4, 2015 5:13 AM