When trying to receive an XML document from a Receive Port, it occurs the following error message and the message is suspense:
“… 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: “portname” URI: “uri” Reason: This Assembler cannot retrieve a document specification using this type: namespace#rootnode …”
This is a strange behavior because the schema was deployed
Cause
- The Application made a reference to another Application that contained one schema with same namespace#rootnode name
- The Application has different resources (DLL) that contained more than one schema with the same namespace#rootnode name
- The schema defined by namespace#rootnode does not exist (not my case, because it was deployed)
Solution
- You need to change the namespace or the root node of one of the schemas. If it’s a common schema, you can deploy it separately to a common application, and add a reference to that application.
In my case, I have one BizTalk Application with 4 resources (DLL), and the problem was that two of these resources (DLL) had one schema with the same namespace#rootnode. I remove one of the schemas and the problem was solved.
Hi Sandro,
I was recenly following your blog! and it was aweome. Can you please help me with this error?
Error: 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: “LEAN MDN
to File” URI: “\aaarcwivsap11630BiztalkDataBizTalk.AS2LEANLoad Status
MDN%MessageID%.txt” Reason: Data at the root level is invalid. Line 1,
position 1.
I have two schemas with different target namespace but same root element: CompositeOperation
I use these schemas for the same WCF-Custom send port to access various stored procedures in the same SQL Server DB. The SOAP Action header is configured to CompositeOperation. That results in the error message mentioned in this blog post. I haven’t found the solution yet.
SendPort9
There was a failure executing the send pipeline: “SBH.BT.MulesoftOracleCE.POSCEOracle, SBH.BT.MulesoftOracleCE, Version=1.0.0.0, Culture=neutral, PublicKeyToken=70943164b7713899” Source: “PosCeAuthorizationComponent” Send Port: “SendPort9” URI: “D:\Deployment\%MessageID%.xml” Reason: The application does not exist.
Getting below error:
SendPort9
There was a failure executing the send pipeline: “SBH.BT.MulesoftOracleCE.POSCEOracle, SBH.BT.MulesoftOracleCE, Version=1.0.0.0, Culture=neutral, PublicKeyToken=70943164b7713899” Source: “PosCeAuthorizationComponent” Send Port: “SendPort9” URI: “D:\Deployment\%MessageID%.xml” Reason: The application does not exist.