Symptoms
When you use the Electronic Data Interchange (EDI) pipeline to receive EDI interchanges in Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009, you may receive the following error message in the Application log:
Event Type: ErrorEvent Source: BizTalk Server 2009 EDIEvent Category: NoneEvent ID: 8114Description:Error encountered during parsing. The X12 transaction set with id '<n>' contained in functional group with id '<n>', in interchange with id '<n>', with sender id '<sender id> ', receiver id '<receiver id>' is being suspended with following errors:Error: 1 (Field level error) SegmentID: DTM Position in TS: 42 Data Element ID: DTM02 Position in Segment: 2 Data Value: leapdate 8: Invalid Date
This issue only occurs when you receive EDI X12 (including HIPAA) interchanges. This issue does not occur when you use EDI EDIFACT interchanges.EDI Type (Data Element) Validationhttp://msdn.microsoft.com/en-us/library/bb226537(BTS.20).aspxNotes
-
The Event Source is "BizTalk Server 2006 EDI" if you are using BizTalk Server 2006 R2.
-
The placeholder leapdate represents a leap date that is contained in the EDI interchange.
Cause
This issue occurs because the EDI interchange cannot validate a data element that contains a leap date value. For example, this issue occurs if the EDI interchange contains the "20120229" date value.
Resolution
Cumulative update information
BizTalk Server 2009
The hotfix that resolves this issue is included in cumulative update package 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
BizTalk Server 2006 R2
The hotfix that resolves this issue is included in cumulative update package 4 for BizTalk Server 2006 R2 SP1. 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:2682056Cumulative update package 4 for BizTalk Server 2006 R2 SP1
Hotfix information
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 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 website:
http://support.microsoft.com/contactus/?ws=supportNote 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.
Prerequisites
You must have BizTalk Server 2006 R2 Service Pack 1andCumulative update package 3 for BizTalk Server 2006 R2 Service Pack 1 installed to apply this hotfix.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
File information
File information for all supported versions of BizTalk Server 2006 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Microsoft.biztalk.edi.messagecore.dll |
3.6.2230.12 |
350,088 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.edi.pipelinecomponents.dll |
3.6.2230.12 |
190,352 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.edi.reporting.common.dll |
3.6.2230.12 |
25,488 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.edi.reporting.dll |
3.6.2230.12 |
55,168 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.edi.schemaeditorextension.dll |
3.6.2230.12 |
202,648 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.edi.shared.dll |
3.6.2230.12 |
161,656 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.ediint.reporting.dll |
3.6.2230.12 |
34,696 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.messaging.dll |
3.6.2230.12 |
92,024 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.pipeline.components.dll |
3.6.2230.12 |
292,752 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.pipeline.dll |
3.6.2230.12 |
292,728 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.streaming.dll |
3.6.2230.12 |
51,064 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.biztalk.xpathreader.dll |
3.6.2230.12 |
79,744 |
28-Jan-2011 |
18:14 |
x86 |
|
Microsoft.xlangs.basetypes.dll |
3.6.2230.12 |
104,312 |
28-Jan-2011 |
18:14 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
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
