-
Title
vRanger failing to connect to service after upgrading to 5.3 -
Description
After upgrading to vRanger 5.3 via upgrade package, vRanger GUI doesn't start throwing "Could not connect to service" error even though all vRanger services are running.
-
Cause
vRanger database wasn't properly upgraded to version 5.3 because of either UAC preventing execution of SQL scripts or GPO (group policies) or the combination of both.
-
Resolution
1. If UAC is present (Windows Server 2008/2008R2 or Windows 7) disable UAC completely.
2. Restart Windows.
3. Download and install MS SQL Server Management Studio Express (SSMSE).
4. Start SSMSE, connect to vRanger’s DB, go to vRangerPro database, open “ConfigurationOption” table and set “LastUpgradedVersion” to 5.2.0.0.
5a. If vRanger 5.3 is still installed, run “vRanger Database” utility and do the usual steps.
5b. If vRanger was uninstalled (but its database is still in place), run full installation package and do the usual steps.
6. If 5a step was chosen, restart vRanger Service.
-
Defect ID
13344 -
Additional Information
Microsoft SQL Server Management Studio Express (SSMSE): http://www.microsoft.com/download/en/details.aspx?id=8961