Article ID: 946208 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
You try to add a delegate to another user's mail box in Microsoft Office Outlook 2003. When you do this, the delegate is not added. Additionally, you receive the following error message:
This problem occurs when the global catalog to which you are connected is not writable to the current user.
The Delegates settings were not saved correctly. Unable to activate send-on-behalf-of list. You do not have sufficient permission to perform this operation on this object.
For a detailed explanation about scenarios that could lead to a non-writable global catalog, see the "Understanding multidomain DL update and delegate issues after application of Exchange 2003 SP2" topic. To do this, visit the following Microsoft Web site:
How to obtain the hotfixThis issue is fixed in the Outlook 2003 post-Service Pack 3 Hotfix Package that is dated December 13, 2007. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
946207After you apply the hotfix and the registry data that is listed below, you can add a delegate that does not have write permission to the global catalog. When you do this, an informational message that resembles the following message is logged in the Application log to help track the event:
(http://support.microsoft.com/kb/946207/ )Description of the Outlook 2003 post-Service Pack 3 hotfix package: December 13, 2007
How to enable the hotfixTo enable the hotfix, you must add the IgnoreSOBError setting to the registry.
To have us enable the hotfix for you, go to the "Fix it for me" section. If you prefer to enable the hotfix yourself, go to the "Let me fix it myself" section.
Fix it for meTo enable the hotfix automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.
Fix this problem
Collapse this imageExpand this image
Microsoft Fix it 50900
Collapse this imageExpand this image
Then, go to the "Did this fix the problem?" section.
Let me fix it myselfTo enable the hotfix, follow these steps.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Did this fix the problem?
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For the complete feature set of a delegate, Outlook must set an Active Directory directory service attribute for the user. This attribute is called publicDelegates. The publicDelegates attribute corresponds to the "Send on Behalf of" permission for the delegate.
Before this hotfix was created, the "Send on Behalf of" permission was considered a mandatory part of adding a delegate. This hotfix lets you add the delegate without setting the "Send on Behalf of" permission.
Notice that the "Send on Behalf of" permission is not needed for meeting-related messages. Microsoft Exchange Server specifically does not require that you have "Send on Behalf of" permissions to send a meeting request on behalf of another user. Therefore, even without the "Send on Behalf of" permission, delegates can successfully send meeting requests on behalf of the calendar owner.
However, when you use a delegate that does not have the "Send on Behalf of" permission to send a non-meeting-related message on behalf of the owner, the operation fails. For example, if a delegate wanted to send an informational message "from the boss," that operation would fail. This is because the "Send on Behalf of" permission was not successfully granted.
If the global catalog is not writable to the user of the Outlook client, and if you use this hotfix to add a delegate without setting the "Send on Behalf of" permission, you can add the "Send on Behalf of" permission by using Exchange System Manager. To do this, use the Delivery Restrictions button on the Exchange General tab of the Mailbox properties. For more information about the Exchange General tab, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/aa997251.aspxTo understand how this hotfix works, consider the following scenario:
For more information about how to manage meetings and e-mail messages for your manager, see the "Manage meetings and e-mail for your manager" topic. To do this, visit the following Microsoft Web site: