Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Consider the following scenario:

  • You use the native Electronic Data Interchange (EDI) components in Microsoft BizTalk Server 2009 to receive EDI messages.

  • You receive incoming EDI messages that use multiple schemas. For example, an incoming message uses the 837 Professional 5010 Schema.

  • The message fails at the EDI pipeline, and the EDI message instance is suspended.

In this scenario, no helpful error information is generated. However, an error message that resembles the following is logged in the BizTalk Server Administration Console event log:

An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:


The sequence number of the suspended message is 1.


This issue occurs because of a problem in the subdocument break-splitting logic that is used in multiple schemas.


Cumulative update information

The fix for this issue is included in Cumulative Update 7 for BizTalk Server 2009.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


See a similar issue in Microsoft BizTalk Server 2010.

See a similar issue in Microsoft BizTalk Server 2006 R2.

See BizTalk Server hotfixes and Cumulative Update support for more information.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!