Link to home
Start Free TrialLog in
Avatar of rthesse
rthesse

asked on

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.

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."

I had an Exchange server 2003 standard crash & had to rebuild as a member server. The crashed server was an AD & PDC.  Since that time I am unable to assign delegates to any mailbox without receiving the previous error.  This problem appears to be related to the change in the exchange server being reincarnated as a member server.  I had to do a forced move of all FSMO roles to another controller when the problem occurred.  Any help is appreciated.

Thanks
ASKER CERTIFIED SOLUTION
Avatar of Karl12347
Karl12347
Flag of United Kingdom of Great Britain and Northern Ireland 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
I had a similar issue with a new user this morning on my exchange server and this solved it immediately. Good thinking Karl, much appreciated!
Avatar of rthesse
rthesse

ASKER

Thanks the answer was spot on!
I had a similar issue with our exchange server and a single user, the solution worked perfectly.

Thanks Karl
Got the same issue going on but this Karl's solution isn't fixing it.

The server I'm working was rebuilt earlier this year, but not by me. I have a feeling that some extra security measures were taken to lock down the system a little tighter than is necessary.

The initial red flag that is making me believe that's the case is that inheritable permissions have been disabled for users. Should they be??
Thanx, solved my problem!!!
Thanks man, this solution worked for me like a charm!
Worked for me.  Many thanks
This worked for me too, thank you.
This also worked for me after an Exchange Rebuild.  Thanks!
User had this problem on an existing Exchange 2003 SBS server with Outlook 2010. This solved the problem a treat.
THANK YOU. All other Google searches/fixes proved futile.