I had the same error and had to do some testing together with support. The root cause could not be identified. But the following steps "helped":
- Create a domain security group for each solarwinds security role if not already done so
- Make sure the domain controller replication is done
- Keep the names simple: no special characters and not too long. You should be able to change it afterwards as internally the SID is used.
- Even if you do not need every security rule: do it. If the following does work to bypass the error you will never have to deal with it again.
- Identify which account is used by the "EminentWare Data Grid Server" service
- I use a domain account
- I'll refer to it as "GridUser" for this article
- Get the password for it
- If you need to change the password please see http://knowledgebase.solarwinds.com/kb/questions/3626/Changing+the+account+or+password+used+for+the+Patch+Manager+service for the details on how to do this.
- Log in to your Patchmanager server as GridUser
- Ensure that this user has full control on "C:\Program Files\EminentWare\Server\EminentWare.BusinessObjects.xml"
- Restart the "EminentWare Data Grid Server" service
- Do not restart the whole server
- Log In to the management console
- Try adding the created security groups to the security roles
This did the trick for me. But: I had to do the last three steps twice.