Do those other groups have level lower than 32?
Does you account that you login to EEM, have all neccessary privledges and level higher than those groups that you are trying to manage?
Yes, All other admin accounts have lower then 32 level previliges. The accounts I have used to attempt this have the highest privilidges with all options checked. This was functioning fine prior to me updating to 5.2.4 couple of days ago and moving the object directory and functionality over to a new server.
To breifly summarize here is what led to the issue.
A new server was introduced with majority of the EE Best practices recomendations enabled on the server OS.
Installed 5.2.4 on to a new server (same EEM\EEPC options as what was being used in 5.1 ver)
Restored the sbdata directory over from old server to new server
Started sbdbserver service and tested most of the response functionality all seem to be working. Today when attempting to provide access to a group I experienced the above mentioned error.
If you try to create NEW groups with the same settings as the old ones (that you have problem with), can they be managed without error?
Peter I've tried this and result is the same. The issue just doesnt seem to be with level 32 accounts but any other accounts who have rights to do this. I created new account and even existing accounts to test this. Made sure they all had rights to perform the function. Seems to be just the feature of "Adding" Groups that is throwing this error. How ever I can remove any groups just fine. Wonder if there is a any way to find a particular file within the object directory that can be restored to fix this feature...
if the account you are using has group restrictions, you won't be able to add groups to other accounts (or groups). Is it possible someone has applied group restrictions to all your users?
If so then you'll have to request disaster recovery services from your platinum support person, there's no way to bypass the system (or restore an account from an earlier backup prior to this change being made).
Hello Simo. There are no group restrictions applied to these accounts. They have access to adminster every aspect of our environment. The strange thing is that I can remove groups but cant add. I've tested several other admin functions and most seem to be working just fine. This feature is the only thing that is throwing the insufficient privlidge error. Can I restore a directory or folder within the sbdata from older backup that might fix this specific feature? I've opened a case on this.
sorry to go back to it, but being able to remove groups but not add them is exactly what we would expect if you had group restrictions set on the accounts.
You can't really tinker with the database too much, though you can restore a WHOLE user directory from a previous backup. All that's doing though is removing any potential group restrictions, but you say you don't have group restrictions enabled for those users?
That is correct. The super user accounts do not have any group restrictions applied.