Browse by Tags

Native serialization error Root element is missing Map Error

Recently I was testing a BizTalk map inside Visual Studios. The input schema was auto generated using the SQL Adapter and the output was a simple text file. I was using a sample file provided to me from a past generation from the schema (or so I thought) to test the map. When I was testing, I keep getting a blank file as output and a strange error. The error was: Native serialization error: Root element...

Published Tue, Aug 15 2006 11:01 PM by Stephen W. Thomas

Filed under: biztalk errors, maps

Convoys, GetTempFileName, and InterceptorException in Biztalk Server

It’s late on a Friday. I am still at the client site. I just canceled my flight home. It is my anniversary weekend (yep it is on 9/11, sure sucks). We are hours from going live... But, what does Exceptions.Types.InterceptorException GetTempFileName Failed mean? I ran into this problem while testing some recently updated Orchestrations that use Convoys to process messages received from multiple...

Published Fri, Sep 9 2005 7:12 PM by Stephen W. Thomas

Filed under: biztalk, biztalk errors, convoy

Large Messages Can Cause Large Problems in BizTalk

Recently I have seen a lot of talk about large message support in BizTalk 2004. The most interesting and depressing was on the BizTalk Core Engine WebLog . It seems that large messages do not work as well in BizTalk 2004 as I would have hoped. I have had success with some types of large messages using the file adapter and mapping. I have gotten it to work with messages up to 500 MB but in a production...

Published Wed, Mar 30 2005 3:33 AM by Stephen W. Thomas

Filed under: biztalk errors, biztalk 2004, large messages

XLANGs.BTEngine.BTXTimerMessages Delivered, Not Consumed

What? How? When? Why? Useless? You have no clue what I am talking about? What are BTXTimerMessages? They are messages BizTalk uses internally to control timers. This includes the delay shape and scope shapes with timeouts. How will you see BTXTimerMessage? You will see these messages in HAT. They will be associated with running Orchestations. If they show up, they will be in the Delivered, Not Consumed...

Published Thu, Nov 18 2004 2:32 AM by Stephen W. Thomas

Filed under: biztalk errors

How to Allow Unrecognized Messages on Send Ports Using Message Context

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...

Published Fri, Oct 8 2004 1:32 AM by Stephen W. Thomas

Filed under: biztalk errors, orchestration, context

Root Node Type Name Vs Node Name

I just wanted to take a second to get everyone on the same page since these properties are VERY important in BizTalk. If you are a solo developer or you have never renamed a root node, then you may not understand the importance of these properties. First off, what are they? Node Name: This is the name that is displayed inside Visual Studio for the root node in the schema and for each field element...

Published Thu, Jul 29 2004 5:08 AM by Stephen W. Thomas

Filed under: biztalk, schema, root node, biztalk errors

Syndication

Recent Posts

Tags

Archives