Assume that you are using Electronic Data Interchange (EDI) in Microsoft BizTalk Server. When you process the EDI message from the Extensible Markup Language (XML) to a flat file in the EDI send pipeline, you may notice that the process fails if the message contains an empty node in a sub-loop. For example, the node is denoted as <ns0:DTM_SubLoop/> instead of <ns0:DTM_SubLoop></ns0:DTM_SubLoop>.
Additionally, you may receive an error message that resembles the following:
Log Name: Application
Source: BizTalk Server
Event ID: 5743
Task Category: BizTalk Server
Classic User: N/A
Description: The adapter failed to transmit message going to send port "SendPort1" with URL "FilePath\FileName". It will be retransmitted after the retry interval specified for this Send Port. Details:"Unable to read the stream produced by the pipeline.
Details: Error: 1 (Segment level error)
Position in TS: 36 2:
Unexpected segment ".
Event Xml: <Event xmlns="FilePath\FileName">
<Provider Name="BizTalk Server" />
<TimeCreated SystemTime="Date/Time" />
<Data>Unable to read the stream produced by the pipeline.
Details: Error: 1 (Segment level error) SegmentID: AMT Position in TS: 36 2: Unexpected segment< /Data> </EventData> </Event>
This issue is fixed in the following cumulative updates for BizTalk Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For information about the service packs and cumulative update list for BizTalk Server, click the following article number to view the article in the Microsoft Knowledge Base:
2555976 Service pack and cumulative update list for BizTalk Server
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 hotfixes and Service Pack support