-
Title
Setting vRanger Database permissions -
Description
vRanger will launch under one user account, but not on the one that has been created for it.
-
Cause
This can be caused by the local permissions being set for Ranger to run for the services, but the permissions not being set on the database. -
Resolution
The permission for the DB are set through the SQL Management Studio application which are offered free of charge from Microsoft's site. The versions for SQL Express 2K5 (which is embedded into vRanger) are here:
http://www.microsoft.com/en-us/download/details.aspx?id=8961
1. Use SQL Management Studio to connect to your vRanger SQL instance (it can be local or remote).
2. One connected, go to Security > Logins.
3. Right click Security and choose New Login.
4. If you are using an existing Active Directory account click search and identify that account.
5. On the left you will see the Server Roles and the User Mappings options, here you will define the users permissions and the DB that they should be mappend to. The Server Roles are up to your organization and/or policies, the User Mapping for the account should be mapped to vRangerPro (our DB is named vRangerPro by default unless you have changed that).
6. Click OK.
7. Drill down to Databases > vRangerPro > Security > Users (assuming again you haven't changed the name of the DB from vRangerPro), here you will see the user that you just identified to the Database.
8. You should now be able to go back to your vRanger server and stop the vRanger Servers (vRanger API, FLR, vRanger Service) and restart them and connect to the application using the useraccount of your choosing.