Ranger GUI fails to start after seemingly successful upgrade to version 5.3, 5.4 or 5.5.
From the command prompt run the following to get details:
"X:\Program Files (x86)\Quest Software\vRanger\Service>Vizioncore.vRanger.Service.exe" DEBUG
for version 5.3:
[03/31/2012 10:31:44:1948] vRanger Backup & Replication encountered an error during startup. The exact error message was: Invalid object name 'repositoryNVSD'..
for version 5.4:
[05/23/2012 10:31:44:1948] vRanger Backup & Replication encountered an error during startup. The exact error message was: Invalid object name 'repositoryDDBoost'..
User, that ran upgrade, has incorrect default schema assigned. All objects, created/modified by this user will have incorrect schema. In this particular case table name was vRangerProUser.RepositoryNVSD (or vRangerProUser.RepositoryDDBoost), most of the stored procedures looked as follows: vRangerProUser.<procedure_name>
It happens when during upgrade SQL authentication mode is used, then vRangerProUser is selected twice. On first screen some admin (sa or other) should have been used.
Stop vRanger Service. Use SQL Management Studio to fix. Run attached script. It will:
1. fix user's schema
2. fix table/tables
3. fix stored procedures.
Start vRanger Service. Open GUI.
I described one particular case. Incorrect schema name was 'vRangerProUser'. It can be different but correct one is 'dbo'. Please adjust your commands if necessary.