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???
sailciAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tshearonCommented:
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
0
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?
0
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.