Stephen W. Thomas BizTalk Blog

100% Pure BizTalk
posts - 132, comments - 146, trackbacks - 438

My Links

News

Subscribe to my blog via:


Add to Google

Visit my website at:
www.BizTalkGurus.com

Archives

BizTalk 2004 Samples

BizTalk 2006 Samples

BizTalk Videos

BizTalk White Papers

BizTalkBlogs.com

Great BizTalk Blogs

Other Links

Quick Tip: How to Allow Unrecognized Messages on Send Ports

Have you seen an error that looks like the one below on your Send Pipelines?

There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit" Source: "XML assembler" Send Port: "some location" Reason: This Assembler cannot retrieve document specification by using this type: "namespace#rootnode".

 

This is caused by not having a unique combination of namespace and root node (MessageType).  BizTalk by default does not like unrecognized messages.  The XML Disassembler has a setting to allow unrecognized messages.  But what about sending unrecognized messages?

 

To allow unrecognized messages inside the Send Pipeline, just set the XMLNORM.AllowUnrecognizedMessage message property to True inside a Message Construct shape.  This, of course, assumes you have to construct your output message inside the Orchestration. 

 

The statement inside your Construct shape should look like this:

OutMessage(XMLNORM.AllowUnrecognizedMessage) = true;

Print | posted on Friday, October 08, 2004 12:32 AM |

Feedback

Gravatar

# re: Quick Tip: How to Allow Unrecognized Messages on Send Ports

I'm trying to do the same thing, but the document is going Direct into the Message Box. I want to process a number of different message types, but treat them as XmlDocuments (untyped) in this orchestration. The send port generates an error, but the message goes on the box and the downstream orchestration picks it up just fine. Since it is going into the Message Box, there is no pipeline.

I'll try putting it directly into the message box with the Large Message API. Wish me luck!

Stanford.
11/22/2004 9:55 AM | Stanford Powers
Gravatar

# re: Quick Tip: How to Allow Unrecognized Messages on Send Ports

You can use xmlpassthro pipeline at send port to allow UnrecognizedMessage [xml message] out from orchesrtation.

Correct me... if i'm not sticking topic.
6/22/2005 10:56 AM | Hemant Bhadane
Gravatar

# re: Quick Tip: How to Allow Unrecognized Messages on Send Ports

Hello.

Yes, you are correct. You can and always should use the passthrough pipeline on the Send Port unless you need to Demote Properties or perform other work inside the pipeline. In those cases, you might want to allow unrecognized messages.

Stephen W. Thomas
6/22/2005 11:59 AM | Stephen W. Thomas
Gravatar

# re: Quick Tip: How to Allow Unrecognized Messages on Send Ports

I have the weird problem that we always send a message to a port without having any errors about the message not being recognized. Since two hours however, I get the error you described. After doing some more research I still can't find a reason why this would happen :S

Hope the trick you described here helps.
10/6/2006 1:53 AM | W.Meints
Gravatar

# re: Quick Tip: How to Allow Unrecognized Messages on Send Ports

Excellent solution. Solved to problem of debatching with xpath then sending to pipeline for flat file assembly.
8/28/2008 7:01 PM | Chris Pettit

Post Comment

Title  
Name  
Email
Url
Comment   
Please add 6 and 3 and type the answer here:

Powered by: