• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 534
  • Last Modified:

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???
  • 2
1 Solution
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
Gareth GudgerCommented:
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?
sailciAuthor Commented:
I ended up just pushing out via GPO the registry fix (really not a fix, just ignores the error) outlined in the KB referenced in the error message. Had some users try and they were successful.

To answer tshearon, this was a global across the board issue not a ghost delegate or anything like that. The blog essintially was a repeat of the KB referrenced in the error message, although it did talk about 2010 RBAC but I did not see anything comparable in 2013.

To answer Gudger, EAC not an issue, just an Outlook issue.
sailciAuthor Commented:
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.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now