none
Type Problem RRS feed

  • Question

  • Hi,

    I am using the same schema in two different project but getting the following problem :

    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: "FinancialApprovalAuthority.Port.PeopleSoftRequest_SolicitResponsePort" URI: "oracledb://PSTQA" Reason: This Assembler cannot retrieve a document specification using
     this type: "http://Microsoft.LobServices.OracleDB/2007/03/SYSADM/View/PS_TRX_RPT_VW#Select". 

    The type is same for both project.

    But when I changed the pipeline from XMLTransmit to Pass Thru Transmit, I am not facing this error why ?

    Give me any solution.


    Prakash

    Thursday, August 14, 2014 10:33 AM

Answers

  • Hi,

    1. This is the common error you will get if are using same schema for more then 1 project.

    Solution of this is

    either

    deploy the schema seperately in a common application and then take the reference of that application in both applications

    or

    use documentspecnames property of xml transmit pipeline to avoid conflict.

    2. Since pasthru transmit has no components thats why you are not facing this error in that case.

    Regards

    • Marked as answer by Angie Xu Wednesday, August 20, 2014 1:30 AM
    Thursday, August 14, 2014 11:59 AM
  • Based on your description, it is because you have the same schema Deployed in two different Projects.  Because of this, Schema name is Ambiguous (there are two) and the XmlDisassembler will not guess which is correct.

    The XmlDisassembler is the component that resolved the MessageType.  PassThrough does not touch the message at all.

    You have several options:

    1. Deploy the schema in a shared Project and reference it from the other.
    2. In a Custom Pipeline with the XmlDisassembler, Set the Document Schemas property to the proper instance of the Schema.
    3. Change one of the Schema's namespaces.  This would require the incoming message to change as well.
    • Marked as answer by Angie Xu Wednesday, August 20, 2014 1:30 AM
    Thursday, August 14, 2014 12:10 PM

All replies

  • Hi,

    1. This is the common error you will get if are using same schema for more then 1 project.

    Solution of this is

    either

    deploy the schema seperately in a common application and then take the reference of that application in both applications

    or

    use documentspecnames property of xml transmit pipeline to avoid conflict.

    2. Since pasthru transmit has no components thats why you are not facing this error in that case.

    Regards

    • Marked as answer by Angie Xu Wednesday, August 20, 2014 1:30 AM
    Thursday, August 14, 2014 11:59 AM
  • Based on your description, it is because you have the same schema Deployed in two different Projects.  Because of this, Schema name is Ambiguous (there are two) and the XmlDisassembler will not guess which is correct.

    The XmlDisassembler is the component that resolved the MessageType.  PassThrough does not touch the message at all.

    You have several options:

    1. Deploy the schema in a shared Project and reference it from the other.
    2. In a Custom Pipeline with the XmlDisassembler, Set the Document Schemas property to the proper instance of the Schema.
    3. Change one of the Schema's namespaces.  This would require the incoming message to change as well.
    • Marked as answer by Angie Xu Wednesday, August 20, 2014 1:30 AM
    Thursday, August 14, 2014 12:10 PM