Consider the following scenario in Microsoft BizTalk Server 2009:
You use BizTalk Server to process Electronic Data Interchange (EDI) messages from a trading partner.
In the EDI Properties page of the partner party, you enable the Check for duplicate ISA13 (Interchange control number) option on the X12 Interchange Processing properties page.
You receive an incoming EDI message from the partner. This message contains errors. This message is then suspended in BizTalk Server.
The partner corrects the errors of the EDI message, and resends the corrected EDI message to you. Additionally, the ISA13 segment remains unchanged.
In this scenario, the corrected EDI message is suspended in BizTalk Server. Additionally, an event that resembles the following is logged in the Application log:
Event Type: ErrorEvent Source: BizTalk Server 2009 EDIEvent Category: NoneEvent ID: 8112Description:Error encountered during parsing. The X12 interchange with id '<n>', with sender id '<sender id>', receiver id '<receiver id>' had the following errors:Error: 1 (Miscellaneous error) 25: Duplicate Control NumberError: 2 (Field level error) SegmentID: Position in TS: 1 Data Element ID: Position in Segment: 13 Position in Field: 1 Data Value: <n> 25: Duplicate Control Number
This problem occurs because the interchange control numbers in the ISA13 segment of the suspended EDI messages are still recorded in BizTalk Server. This causes a duplicate detection check to be performed.
After you apply this hotfix and configure the Inbound batch processing option in the EDI properties of the agreement to Split Interchange as Transaction Sets - suspend Interchange on ErrororPreserve Interchange - suspend Interchange on Error, only the interchange control numbers of successfully processed EDI messages will be checked for duplicates.
Note This behavior does NOT apply to the Split Interchange as Transaction Sets - suspend Transaction Sets on Error orPreserve Interchange - suspend Transaction Sets on Error Inbound batch processing options.
Cumulative updated information
For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009.
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:
2429050 Cumulative update package 1 for BizTalk Server 2009
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must have Microsoft BizTalk Server 2009 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
This hotfix contains an SQL script (.sql).Please refer to the "More information" section for notes about how to install BizTalk Server hotfixes. After you apply this hotfix, you have to configure the Inbound batch processing option in the EDI properties of the party to Preserve Interchange - suspend Interchange on Error.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the settings on the X12 Interchange Processing properties page, visit the following Microsoft Developer Network (MSDN) Web site: