Article ID: 888606
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
SYMPTOMS
When you use Collaborative Data Objects (CDO) to programmatically create meetings in Microsoft Exchange 2000 Server, you may experience the following symptom. Meetings are automatically moved one hour ahead in the last week of October.
CAUSE
This problem occurs when all the following conditions are true:
- Users in your organization use e-mail clients such as Microsoft Outlook Web Access. Or users use other devices or programs that use CDO to view and to manage their calendars.
- Your organization is configured to use the Coordinated Universal Time (UTC) time zone. (Coordinated Universal Time is also known as Greenwich Mean Time).
- The month of October has five Sundays.
In the UTC time zone, daylight-saving time occurs on the last Sunday in October. However, a code defect in CDO causes the daylight-saving time adjustment to occur on the fourth Sunday in October. This code defect causes an incorrect daylight-saving time adjustment to occur for the years that have five Sundays in October. For example, for client programs that use CDO to access meeting information, the daylight-saving time adjustment occurs on Sunday October 24, 2004 instead of occurring on October 31, 2004 as you expect.
Note This problem affects the years 2004, 2005, and 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 Microsoft Exchange 2000 Server 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.
Prerequisites
Because of file dependencies, this update requires both the following:
- Microsoft Exchange 2000 Server Service Pack 3 (SP3). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
- The August 2004 Exchange 2000 Server post-Service Pack 3 Update Rollup. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
870540 Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup
Restart requirement
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English 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 tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 17-Nov-2004 09:35 6.0.6617.22 720,896 Cdo.dll 17-Nov-2004 08:03 6.0.6617.22 3,919,872 Cdoex.dll 17-Nov-2004 11:03 6.0.6617.22 3,596,288 Excdo.dll 17-Nov-2004 09:32 6.0.6617.22 745,472 Mapi32.dll
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
Keywords: kbqfe kbhotfixserver kbfix kbexchange2000presp4fix kbbug KB888606
