Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: XMLException error when a batching operation processes EDI messages in BizTalk Server 2010 if the separator is set to the less than sign (<) or to 0x3C

FIX: XMLException error when a batching operation processes EDI messages in BizTalk Server 2010 if the separator is set to the less than sign (<) or to 0x3C

View products that this article applies to.

Symptoms

Consider the following scenario:
  • 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=3.0.1.0, 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.

↑ Back to the top

Cause

This issue occurs because batching operations cannot handle the less than sign (<) char value or the 0x3C value as a separator.

↑ Back to the top

Resolution

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

↑ Back to the top

Status

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

↑ Back to the top

References

For more information about how to configure the Charset and Separators settings, visit the following MSDN website:
How to configure the Charset and Separators settings
For more information about how to configure a batching operation, visit the following MSDN website:
How to configure a batching operation
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information about BizTalk Server hotfixes

↑ Back to the top

Keywords: kbqfe, kbfix, kbexpertiseadvanced, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2580202
Revision : 2
Created on : 9/10/2018
Published on : 9/11/2018
Exists online : False
Views : 432