« Mooninite Sign Promo Costs Turner Broadcasting System and Interference, Inc. $2 Million | Main | India Does Not Have Life Jackets? »

Be Prepared For the Daylight-saving Bug On March 11, 2007

It appears that there is a bug in software programmed prior to 2005 that is used to automatically advance the time in the program, i.e. calendar programs.

For three weeks this March and April, Microsoft Corp. warns that users of its calendar programs "should view any appointments ... as suspect until they communicate with all meeting invitees."

...it's a potential problem in any software that was programmed before a 2005 law decreed that daylight-saving time would start three weeks earlier and end one week later, beginning this year. Congress decided that more early evening daylight would translate into energy savings.

Software created earlier is set to automatically advance its timekeeping by one hour on the first Sunday in April, not the second Sunday in March (that's March 11 this year). [CNN]

It sounds like many things could get messed up if the IT folks at companies are not prepared for this. The issue should mainly be inconvenience to the average consumre, but it could cost companies a lot of money.
"We've been aware of the DST changes since late last year. But the tools and patches keep changing, or weren't available, which made it difficult to create a solid plan," said Warren Byle, a systems engineer at an insurance company. "This change might go smoothly for those who are prepared, but I think it will be the 'Y2K that wasn't' for the rest."

The move could impact time-sensitive applications other than calendaring, such as those that process sales orders or keep track of time cards. Gartner, for example, says the bug could lead to incorrect arrival and departure times in the travel industry and result in errors in bank transactions, causing late payments. In addition, trading applications might execute purchases and sales at the wrong time, and cell phone-billing software could charge peak rates at off-peak hours. [CNet News]

A little further down the article on CNet News:
Microsoft and other software makers have created patches to make their products ready for the switch and have filled Web pages with tips for customers. IT pros and consumers alike have to apply those updates. Otherwise, they will have to deal with electronic clocks that may be off by an hour, for three weeks starting March 11 and again for a week in the fall, when they go back on November 4 instead of October 28.

Dealing with the patches should be straightforward for most consumers. Microsoft released a daylight-saving fix for Windows XP Service Pack 2 on Tuesday, and it is pushing the patch out through the Automatic Updates feature in the operating system. An update is also available for Windows-based cell phones. However, the recently launched Windows Vista doesn't need a patch.

For businesses, getting ready is a different story. It isn't as straightforward to apply updates to Windows PCs and phones in a corporate environment, because of potential compatibility woes. Moreover, there are many other fixes that need to be applied, not just from Microsoft, but also from Oracle, IBM, Red Hat, Hewlett-Packard and other software suppliers.

Companies using Microsoft's Exchange for e-mail, for example, face a real patch challenge. Microsoft has updates for the Outlook and Entourage mail clients, and for Windows Server and Exchange Server--all of which need to be applied in a specific order and in rapid succession. [CNet News]

Just beware that there may be some confusion coming up with regard to meetings, billings and other things that may be affected by this issue. I suggest everyone follows the links in this post that have to do with a system you are operating and get the patch installed. If there is no link of relevance to your system needs, do a search on the net and you will find lots of information.

Here are some links to other posting about this issue by bloggers:

Techie Diva has some links to other software upgrades you may find useful.

BLOG by zaiss Sam Zaiss posts about a first-hand experience with the issue (I found this post via a link from Markus Weickenmeier's blog).

Firehouse has a post with the full AP story included if interested.

Post a comment