Microsoft KB Archive/841639

= Delegate recipient receives two update messages when a meeting request is updated on Exchange Server 5.5 =

Article ID: 841639

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition

-





SYMPTOMS
After you configure Microsoft Outlook to send meeting request messages only to a delegate recipient, all requests, updates, and cancellations to the meeting are sent to your delegate recipient. This is the expected behavior. If a meeting is changed or updated, and if your mailbox is on a Microsoft Exchange 5.5 Server computer, your delegate recipient receives duplicate update messages. If your delegate recipient deletes one of the update messages, the meeting item is removed from your calendar.



CAUSE
When your delegate accepts a meeting request that is sent to a distribution list that you belong to, your individual name is added to the optional attendees list. Because your name appears in the attendees list and in the distribution list, two messages are sent to your delegate when a change or an update is made to the meeting.

Typically, the Exchange Server information store recognizes duplicate messages because they have the same message identifier (MTSID). However, because the delegate rule has been configured for your mailbox, the information store applies the delegate rule for both messages that enter the information store, and then the information store generates two separate messages to send to your delegate. Each new message is assigned a different MTSID. Therefore, the information store does not identify the duplicate messages.

Both the update messages that are sent to your delegate control the meeting item on the calendar. For example, the delegate can use either update message to accept the meeting or to decline the meeting. Therefore, if one of the update messages is deleted, the meeting object is removed from your calendar.



Hotfix information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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
No prerequisites are required.

Restart Requirement
You must 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) 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 --  14-Jul-2004  14:48  5.5.2658.16       496,400  Mdbmsg.dll 14-Jul-2004 14:47  5.5.2658.16     2,635,024  Store.exe



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

817903 New naming schema for Exchange server software update packages

Keywords: kbexchange550presp5fix kbbug kbfix kbqfe kbhotfixserver KB841639

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.