You have a computer that is running Microsoft BizTalk Server 2010.
You set the Component element separator (ISA16) property of the Charset and Separators settings for a party to the less than sign (<) char value or to the 0x3C hexadecimal value.
You configure a batching operation for the processing of Electronic Data Interchange (EDI) messages for the party.
In this scenario, the EDI assembler does not work correctly, and an XMLException is generated. Additionally, an error message that resembles the following is logged in the Application log:
Log Name: Application Source: BizTalk Server Event ID: 5754 Task Category: BizTalk Server Level: Error Keywords: Classic User: N/A Description: 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=220.127.116.11, 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 information
The 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:
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: