• Connect to the database with SQL Server Management Studio Express using local administrator or account with permissions set.
• Expand the Security tab.
• Expand the Logins tab.
• Verify that the Windows domain user that runs the vRanger service is listed.
• Right click select Properties/Server Roles.
• Ensure user has public and sysadmin roles granted.
If not:
• Right click and select New Login.
• Add the account by having the Windows authentication option selected and press the Search button.
• Be sure to set the Default database to vRangerPro.
• Select Server Roles.
• Grant Public & Sysadmin.
• Expand the vRangerPro database.
• Expand the Security tab.
• Expand the Users tab and verify the Windows domain account is not listed.
• Right click and select New User.
• Click the button to the right of the Login name box and locate the vRanger service user.
• Be sure to set the Default schema to [dbo].
• Under Database role membership select db_owner.
• Click OK.
• Exit the Management studio.
• Restart the Quest vRanger services:
• Stop the following services in the following order, vRanger API Service, vRanger FLR Service, and vRanger Service.
• Once all the services are stopped please start the services in the following order, vRanger Service, vRanger FLR Service, and vRanger API Service.
