Microsoft KB Archive/312433

= Accepting or denying a meeting request causes a &quot;5.1.1&quot; non-delivery report in Exchange Server =

Article ID: 312433

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange Server 5.5 Standard Edition

-



This article was previously published under Q312433





SYMPTOMS
Microsoft Outlook lets you configure a delegate for a Microsoft Exchange Server 5.5, Microsoft Exchange 2000 Server, or Microsoft Exchange Server 2003 mailbox. If the delegate that you select is damaged, corrupted, or missing, the following symptoms may occur:  Meeting requests are incorrectly sent to previously-removed delegates. You cannot add a user as a delegate if that user was previously a delegate and then had been removed from the list of delegates.  A non-delivery report (NDR) is generated when a user sends a meeting request to a mailbox because that mailbox has a delegate whose mailbox has been deleted. The NDR will look similar to the following: Your message did not reach some or all of the intended recipients.

The following recipient(s) could not be reached:

User D on 4/4/2005 12:10 PM

The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.

 



CAUSE
This issue can occur when a delegate for a mailbox is damaged, corrupted, or missing. This causes an orphaned delegate. Consider the following example:
 * The mailbox for UserA has UserD configured as a delegate.
 * The Send meeting requests and responses only to my delegates, not to me delegate option in Outlook is enabled.
 * The UserD user account is deleted from Active Directory.
 * In Outlook, UserD no longer appears as a delegate, but the Send meeting requests and responses only to my delegates, not to me check box is selected and appears dimmed (unavailable).

In this scenario, the NDR that is described in the &quot;Symptoms&quot; section is generated.



RESOLUTION
If the removed delegate still receives meeting requests, or if senders of meeting requests receive NDRs, follow these steps first:
 * 1) In Outlook, when you are using the mailbox where the delegate was previously established, click Options on the Tools menu, and then click Delegates.
 * 2) Click Add, and then click the delegate that had been removed if the name of the delegate is available. You can select another user in the Global Address List if the original delegate has been removed. Try to establish the same permissions that were previously used, if you know what they are. Then, click OK.
 * 3) Click OK to close the Options dialog box.
 * 4) Restart Outlook.
 * 5) On the Tools menu, click Options, and then click Delegates.
 * 6) Click to clear the Send meeting requests and responses only to my delegates, not to me check box.
 * 7) Click the delegate that you had re-added, click Remove, and then click OK to close the Options dialog box.
 * 8) Restart Outlook.
 * 9) Send the user a meeting request. Then, make sure that the meeting request was not sent to the former delegate.

If the previous steps are not successful, use Mdbvu32.exe to manually remove the delegate rule. Mdbvu32.exe is a message store viewer utility that uses Extended MAPI. You can find the Mdbvu32.exe utility on the CD of each version of Exchange.

To identify a delegate rule and remove the delegate rule from a mailbox, follow these steps:
 * 1) Make sure that Outlook is not currently running on the workstation.
 * 2) Start the Mdbvu32.exe utility, and then click OK in the first dialog box, to log on.
 * 3) On the MDB menu, click OpenMessageStore.
 * 4) Click the relevant mailbox, and then click Open to start the store.
 * 5) On the MDB menu, click Open Root Folder.
 * 6) Double-click Top of Information Store in the Child Folders area.
 * 7) Double-click Inbox in the Child Folders area to view the properties of the Inbox folder.
 * 8) Locate the Associated Message in FLD: pane of the MAPI_FOLDER-Inbox window. Notice the items that start with *pb EF 00 00 00 19 82 62. Each of these is a rule that is set up on the Inbox. The user can set up some of the rules. Other rules are for things like using the Out of Office Assistant or forwarding meeting responses to a delegate.
 * 9) Double-click each of the rules in turn, to open the rule and examine the rule to determine which rule is the delegate rule. Check the Message Property 0x65EB. The delegate rule should have the Schedule + EMS Interface for this property.
 * 10) When you find the corresponding rule, check the message property 0x65EF, which is a long, double-byte string of characters. If the string starts with 02, the rule states, &quot;Send meeting requests and responses only to my delegates, not to me.&quot; If the string starts with 01, the rule states, &quot;Delegate receives copies of meeting-related messages sent to me.&quot; If either of these options is set in Outlook, and there is no message or rule under Associated Message in FLD:, the rule no longer exists, which explains why the requests and responses are not being forwarded. You can also delete the delegate rule from here.
 * 11) After you identify the delegate rule, select the rule in the Associated Message in FLD: pane of the MAPI_FOLDER-Inbox window.
 * 12) In the Operations available box, click lpFld->DeleteMessages, and then click Call Function.
 * 13) When the MAPI_FOLDER-Inbox->DeleteMessages window appears, click OK to delete the message.
 * 14) Quit Mdbvu32.exe by closing all windows until you return to the MDB Viewer Test Application window.
 * 15) On the MDB menu, click Store Logoff, and then click OK.
 * 16) Click OK in the LOGOFF_COMPLETE window.
 * 17) Close the MDB Viewer Test Application window.

Additional query words: XFOR

Keywords: kbenv kbinfo KB312433

-

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

© Microsoft Corporation. All rights reserved.