Microsoft EDI Leap Year Hotfix for BizTalk Server 2009 and 2006 R2 – FIX: “Invalid Date” error occurs when you use the EDI pipeline to receive EDI interchanges in BizTalk Server 2006 R2 or in BizTalk Server 2009 if a data element contains a leap date value

Posted: February 25, 2012  |  Categories: Administration BizTalk

Please treat this as an Important Fix (on the line of Security updates) for all 2006 R2 and 2009 BizTalk servers.

This fix needs to be applied ASAP (before next week) as we will be hitting the leap year date 2/29/2012 in just about a week

This fix should be applied in:

  • Microsoft BizTalk Server 2006 R2
  • Microsoft BizTalk Server 2009 without CU installed (The fix has been available for quite some time and also included as part of the CU for BizTalk 2009 since CU1).

If you are not using X12 in your EDI transactions, this issue is not applicable to you and hence you don’t have to worry about taking this fix at this time.  The fix is only on the x12 code path and does not affect EDIFACT processing.

Problem

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:

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

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.

Hotfix

Original post by Guru Venkataraman (BizTalk Customer Response Team) here and here.

Problem encountered during the install of the BizTalk EDI Leap Year Hotfix

  • “The patch 861c5534-6cfa-4dcf-ba70-cbf01129b646 in the package Microsoft BizTalk Server 2006 R2 Hotfix [See KB article 2435900 for detail] cannot be applied. The minimum installed version of Microsoft BizTalk Server 2006 must be 3.6.2222.12. The installed version on this computer is 3.6.1404.0.”.

Note: you need to install this hotfix with a user with administrative privileges on the machine.

What do I do if I did not get the Leap Year Fix installed in time?

Check Guru Venkataraman (BizTalk Customer Response Team) post here!

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published.

BizTalk360
BizTalk Server

Over 650+ customers across
30+ countries depend on BizTalk360

Learn More
Serverless360
Azure

Operate efficiently with enterprise-grade Azure monitoring,
tracing, remediation & governance in one platform

Learn More

Back to Top