Link to home
Start Free TrialLog in
Avatar of sailci
sailciFlag for Afghanistan

asked on

Unable to Add Delegate in Outlook 2010

kb2593557 referenced in the 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.

We have a single domain with multiple GCs. The problem right now would appear to be affecting all users. The problem is new, things worked in the recent past. The only change that I can think of is I introduced a second mailbox/cas server and created a DAG. So I checked to see if any Outlook clients were connecting to this second server and perhaps the issues lied there somehow, but Get-Counter “\MSExchange RpcClientAccess\User Count” -ComputerName exserver1, exserver2 | ft as well as Get-Counter “\MSExchange OWA\Current Unique Users” -ComputerName exserver1, exserver2|ft show all connections are to exserver1 the primary server. As for the SELF object, it is present and has "Write Personal Information" right.

Not sure what else to check???
Avatar of tshearon
tshearon
Flag of United States of America image

You can sometimes get this when a mail user that no longer exists is still in the delegates list. You can remove and then it works if that is the case. But that's probably not the issue since you say it's affecting everyone. You can try this: http://blogs.technet.com/b/mspfe/archive/2012/06/26/solving_2d00_the_2d00_delegates_2d00_settings_2d00_were_2d00_not_2d00_saved_2d00_correctly_2d00_error_2d00_on_2d00_exchange_2d00_2010.aspx
Avatar of Gareth Gudger
You mentioned you tried to do this through Outlook directly. What happens if you try and add the Send on Behalf permission through EMC/EAC instead?
ASKER CERTIFIED SOLUTION
Avatar of sailci
sailci
Flag of Afghanistan image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sailci

ASKER

No other solution provided. The workaround I implemented as a result of the KB article that the error message referenced solved the issue satisfactorily enough to move on and close this out.