you need to use the cleanupusergroup command of the API to fix these objects.
1 of 1 people found this helpful
I am guessing there are some file rights problems in your environment then - are you using a local or remote connection to the database?
It was a rights problem. I forgot to run the cmd.exe with administrator rights (right click run as admin) in Windows server 2008r2. It is fixed now, thanks a lot for your help.