Article ID: 2580202 - View products that this article applies to.
Consider the following scenario:
Log Name: Application
Source: BizTalk Server
Event ID: 5754
Task Category: BizTalk Server
A message sent to adapter "FILE" on send port "<send port name>" with URI "<URI>" is suspended.
Error details: There was a failure executing the send pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiSend, Microsoft.BizTalk.Edi.EdiPipelines, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI Assembler" Send Port: "<send port name>" URI: "<URI>" Reason: Name cannot begin with the '<' character, hexadecimal value 0x3C. Line 1, position 430.
Note This issue does not occur if you set the Component element separator (ISA16) property to the colon (:) char value or if you do not configure a batching operation for EDI messages.
This issue occurs because batching operations cannot handle the less than sign (<) char value or the 0x3C value as a separator.
Cumulative update informationThe hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2010.
For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2573000/ )Cumulative update package 2 for BizTalk Server 2010
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to configure the Charset and Separators settings, visit the following MSDN website:
How to configure the Charset and Separators settingsFor more information about how to configure a batching operation, visit the following MSDN website:
How to configure a batching operationFor more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2003907/ )Information about BizTalk Server hotfixes
Article ID: 2580202 - Last Review: August 31, 2011 - Revision: 1.0
Contact us for more help