This Assembler cannot retrieve a document specification

 

The most common cause of following errors are if same schema deployed multiple time in BizTalk. Sometimes this is desirable behavior, for example, if same schema is shared by two different BizTalk application.

Since BizTalk applications are just logical grouping of BizTalk artifacts, schemas deployed for one application will be visible to other applications and might create this type conflict.

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

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: "PCISendPort" URI: "oracledb://x:1521/X/Dedicated" Reason: This Assembler cannot retrieve a document specification using this type: http://Microsoft.LobServices.OracleDB/2007/03/PC/Package/STORED_PROCEDURES_2#STOP_LIST

There was a failure executing the response(receive) pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Send Port: "PCISendPort" URI: "oracledb://x:1521/PCI/Dedicated" Reason: Cannot locate document specification because multiple schemas matched the message type http://Microsoft.LobServices.OracleDB/2007/03/PC/Package/STORED_PROCEDURES_2#STOP_LISTResponse.

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

Solution:

Create a new send port for service, go to send pipeline properties and set DocumentSpecNames property to fully qualified name of schema in format <schema type>+<root name> ,<schema assembly full name>. This Pipeline property tells BizTalk exact location of schema to be loaded and thus avoid conflict

for example: ReportLostV2.CardReportLostPC_Package_STORED_PROCEDURES_2+STOP_LIST, Card.ReportLostV2, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9b51853b6987xxxx

 

SNAGHTML5cba62b

 

you can get DocumentSpecNames value from SchemStrongName context property.

SNAGHTML5d11072

Advertisements