vRanger database is marked as "suspected" (4045923)

vRanger doesn't start throwing "Could not connect to service" error. When checked in MS SQL Server Management Studio [Express], vRanger's database is shown as "suspected".

A database can be marked suspect for one of the following reasons:

• If one or more database files are not available.
• If the entire database is not available.
• If one or more database files are corrupted.
• If a database resource is being held by the operating system.

1. Open up MS SQL Server Management Studio [Express], click on "New Query" button and then run the following query:

EXEC sp_resetstatus 'vRangerPro';
ALTER DATABASE vRangerPro SET EMERGENCY
DBCC checkdb('vRangerPro')
ALTER DATABASE vRangerPro SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB ('vRangerPro', REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE vRangerPro SET MULTI_USER

2. Re-run vRanger Database Setup.

3. Restart vRanger services.