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
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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.
|
2006 | March 31 | October 1 |
2007 | March 30 | Not available |
2008 | March 28 | Not available |
2009 | March 27 | Not available |
2010 | March 26 | Not 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.
|
Cdo.dll | 6.5.7651.24 | 717,312 | 18-May-2006 | 00:34 | x86 |
Cdoex.dll | 6.5.7651.24 | 3,945,472 | 18-May-2006 | 02:05 | x86 |
Excdo.dll | 6.5.7651.24 | 3,630,592 | 18-May-2006 | 02:05 | x86 |
Exoledb.dll | 6.5.7651.24 | 2,609,664 | 17-May-2006 | 13:28 | x86 |
Exwform.dll | 6.5.7651.24 | 694,784 | 18-May-2006 | 00:53 | x86 |
Madfb.dll | 6.5.7651.24 | 525,312 | 18-May-2006 | 02:05 | x86 |
Massync.dll | 6.5.7651.24 | 756,224 | 18-May-2006 | 01:06 | x86 |
Rtdsmcal.dll | 6.5.7651.24 | 32,256 | 18-May-2006 | 00:55 | x86 |