Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

After you configure the Jerusalem time zone settings to match the transition dates for daylight saving time, meetings are moved ahead by one hour when a user accepts a meeting request by using a CDO program in Exchange Server 2003


View products that this article applies to.

Symptoms

Consider the following scenario. You use the TZEdit tool to customize the Jerusalem (GMT + 02:00) time zone settings in an organization that is running Microsoft Exchange Server 2003. You configure the time zone settings to match the official transition dates for daylight saving time that were announced for 2006. You send a meeting request to a user in the organization. Then, the user uses a CDO program, such as the Auto Accept agent or Microsoft Outlook Web Access, to accept the meeting request. In this scenario, the time of the meeting is moved ahead by 1 hour. This problem occurs when the meeting is scheduled between the following dates:
  • Between March 26 and March 31, 2006
  • Between October 1 and October 29, 2006

↑ Back to the top


Cause

This problem occurs because the CDO time zone tables differ from the Microsoft Windows time zone tables. Therefore, the daylight saving time transition dates are not correctly resolved.

↑ Back to the top


Resolution

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. 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.

Hotfix installation information

After you install the hotfix, the daylight saving time transition dates are correctly resolved for the Jerusalem time zone for the year 2006. Additionally, the start date of daylight saving time is also resolved for several years. However, because the end date of daylight saving time is not based on the Gregorian calendar, this problem is not resolved in the years following 2006. The following table lists the dates that CDO programs will correctly interpret as daylight saving time transition dates after you apply this hotfix.
YearStart dateEnd date
2006March 31October 1
2007 March 30 Not available
2008March 28Not available
2009March 27Not available
2010March 26Not available

Prerequisites

You must install Microsoft Exchange Server 2003 Service Pack 2 (SP2) before you install the hotfix.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003

Restart requirement

You do not have to restart the computer after you apply the hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The global 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.
File nameFile versionFile sizeDateTimePlatform
Cdo.dll6.5.7651.24717,31218-May-200600:34x86
Cdoex.dll6.5.7651.243,945,47218-May-200602:05x86
Excdo.dll6.5.7651.243,630,59218-May-200602:05x86
Exoledb.dll6.5.7651.242,609,66417-May-200613:28x86
Exwform.dll6.5.7651.24694,78418-May-200600:53x86
Madfb.dll6.5.7651.24525,31218-May-200602:05x86
Massync.dll6.5.7651.24756,22418-May-200601:06x86
Rtdsmcal.dll6.5.7651.2432,25618-May-200600:55x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

In 2005, Israel amended the law that affects the dates for daylight saving time. Now daylight saving time will start on the last Friday before April 2 at 02:00 A.M. Daylight saving time will end on the Sunday before the tenth day of the Jewish month of Tishrei, at 02:00 A.M. This decision causes the transition dates for daylight saving time to occur on the following dates.
YearStart dateEnd date
2006March 31October 1
2007 March 30 September 16
2008March 28October 5
2009March 27September 27
2010March 26September 12
For more information about the terminology that Microsoft uses for software that is corrected after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about the naming schema for Exchange software updates, click the following article number to view the article in the Microsoft Knowledge Base:
817903 New naming schema for Exchange Server software update packages

↑ Back to the top


Keywords: KB916989, kbbug, kbfix, kbqfe, kbhotfixserver, kbautohotfix, kbarchive, kbnosurvey

↑ Back to the top

Article Info
Article ID : 916989
Revision : 4
Created on : 1/15/2015
Published on : 1/15/2015
Exists online : False
Views : 232