All or most backup jobs fail with a "The database trasaction OR transaction was rolled back" message (4043312)

vRanger backup or replication tasks fail with the message "Error: The database transaction was rolled back".

This issue can happen in the following scenarios:

• If vRanger has been installed in an external SQL server, the disk where the database resides is full.
• If vRanger has been installed using the embedded SQL Express instance, it may have reached the 10 GB limit for the databases. This limit is enforced in the SQL Express editions.

• The PurgeDB script can be executed in SQL Management Studio or SQLCMD.

• The Quest vRanger service must be in a stopped state.

• It will purge corresponding records and shrink the database. Only unnecessary obsolete records will be deleted.

1. Please make sure no backups/replications jobs are running. 
2. Stop vRanger services from top to bottom (Start -> Run -> Services.msc -> Quest vRanger service). 
3. Backup the current vRanger DB, 
4. Start SQL Management Studio and connect to the SQL instance.
   1.  Click on the plus next to Databases
   2.  Right-click on the vRangerPro DB, click on Tasks, and click on Back Up...
   3.  In the backup wizard, you can change the location of the backup destination if you do not want to use the default path and press "Ok".
   4.  Download the PurgeDB script and using SQL Management Studio, Drag-and-Drop it on top of the vRangerPro database to load the script. 
   5.  The script will be default set to run in Test mode, please execute it to confirm it will be successful first, then modify the below settings to run the script
   6. SET @test_run = 1 (Change this to "0" to run the script).
   7.  Execute the script. this time it will take longer compared to the test run.
5. After it completes, you can start the vRanger services from bottom to top. Retry a backup job.