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:
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:
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.
This problem occurs when the global catalog to which you are connected is not writable to the current user.
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:
This 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:
946207 Description of the Outlook 2003 post-Service Pack 3 hotfix package: December 13, 2007
After 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:
Source: Outlook Category: None Event ID: 27 Date: date Time: time Type: Error User: N/A Computer: computer_name
Description: SOB error ignored
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
How to enable the hotfix
To enable the hotfix, you must add the IgnoreSOBError setting to the registry.
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.
Exit Outlook 2003.
Start Registry Editor. To do this, use one of the following procedures:
In Windows Vista, click Start , type regedit in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.
In Windows XP, click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following registry subkey:
After you select the subkey that is specified in step 3, point to New on the Edit menu, and then click DWORD Value.
Type IgnoreSOBError, and then press ENTER.
Right-click IgnoreSOBError, and then click Modify.
In the Value data box, type 1, and then click OK.
On the File menu, click Exit to exit Registry Editor.
Did this fix the problem?
Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.
We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email.
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:
To understand how this hotfix works, consider the following scenario:
You work in a multiple-domain environment in which the global catalog is not writable to the mailbox users.
You try to add a delegate, and the addition fails. You receive the error message that is mentioned in the "Symptoms" section.
You apply hotfix 946208 as described in this article. You set the IgnoreSOBError registry value to enable the hotfix.
You add the delegate again. This time, the addition is completed successfully. Additionally, an event is logged in the Application log that indicates that you added the delegate without granting "Send on Behalf of" permissions. Meeting requests and appointments behave correctly, and the "Send on Behalf of" operation works as expected for calendar functions.
You try to send a non-meeting-related e-mail message on behalf of the mailbox owner. The operation fails, and you receive an error message. This situation occurs because you do not have the "Send on Behalf of" permission.
In this scenario, contact the Exchange Server administrator and ask him or her to use the server administrative tools to add the "Send on Behalf of" permission. After the administrator does this, the complete delegate feature set works correctly.
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: