XADM: "GetAssociatedAppointment" Creates Duplicate Attachments

In the following scenario, duplicate attachments may be created:

�	A user (for this example, User A) uses Microsoft Outlook to send a recurring meeting request to another user (for this example, User B) with an attachment (attachment 1).
�	User B uses Outlook to accept this meeting.
�	User A uses Outlook to edit an occurrence of the meeting, and replaces attachment 1 with another attachment (attachment 2).
�	User A uses Outlook to send an updated meeting request to User B.
�	Collaboration Data Objects (CDO) code is run against User B's Inbox. The Inbox receives the meeting request, calls GetAssociatedAppointment(), and then calls Update() on the appointment.
�	When user B opens the User B Calendar in Outlook, all of the occurrences of the appointment contain both attachments.

In the fifth step in the preceding scenario, if User B uses Outlook to open the Inbox and accept the updated meeting request instead of Collaboration Data Objects (CDO) code running against User B's Inbox, the one edited occurrence contains attachment 2 only, and the other occurrences contain attachment 1 only. CDO should work the same way.

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: The following files are available for download from the Microsoft Download Center:
Release Date: May 16, 2002

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file. The English version of this fix should have the following file attributes or later:

Component: CDO

File name	Version	Date	Time	Size
Cdo.dll	6.0.5770.16	11-Dec-2001	10:47	713,216

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

You must apply this fix (Q314606) after you install Exchange 2000 Service Pack 2 (SP2).