Article ID: 973901 - View products that this article applies to.
Consider the following scenario:
Event Type: Error
Error: 1 (Miscellaneous error) 6: Missing or invalid or duplicate Transaction set identifier 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837_P'
This problem occurs because of a limitation in BizTalk Server. To process an incoming 837 document, BizTalk Server selects a schema by finding a match between the ST1 segment of the incoming document, and the ST1 field in the X12 Interchange Processing Properties page.
For example, you process different kinds of 837 documents (837_D, 837_I and 837_P) that have different schemas. These documents are received from the same sender. You configure the X12 Interchange Processing Properties page to specify the different target namespace for these 837 documents that are marked in the ST1 field. However, according to the HIPAA standard, the ST1 segment of the 837 document can contain a maximum of 3 characters ('837'), and the _D, _I, and _P type is lost. Therefore, BizTalk Server cannot determine which schema to use to process the incoming 837 document.
To resolve the problem, you can apply this hotfix. After you apply this hotfix, BizTalk Server uses both ST1 segment and GS8 segment in the incoming 837 document to match the ST1 filed in X12 Interchange Processing Properties page.
Note GS8 segment indicates which kind of 837 document the incoming 837 document is.
If you have specified schema namespace for 837_D, 837_I and 837_P in X12 Interchange Processing Properties page, BizTalk Server can find the schema to process the incoming 837 documents correctly.
Cumulative updated informationFor 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:
(http://support.microsoft.com/kb/2429050/ )Cumulative update package 1 for BizTalk Server 2009
Hotfix informationA 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 this specific problem.
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, submit a request to 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: -
PrerequisitesYou must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply this hotfix. However, you must restart the BizTalk Host Instance service after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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.
Microsoft BizTalk Server 2006 R2
Collapse this tableExpand this table
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 X12 interchange processing properties, visit the following Microsoft Developer Network (MSDN) Web sites:
http://msdn.microsoft.com/en-us/library/dd801380%28BTS.10%29.aspxFor more information about how BizTalk Server receives an Electronic Data Interchange (EDI) message, visit the following Microsoft Developer Network (MSDN) Web site:
Article ID: 973901 - Last Review: December 8, 2010 - Revision: 2.0