HOWTO: Fix vRanger "The database transaction was rolled back" Error

Update: Andrew G in the comments posted a link to a newer version of this script for newer versions of vRanger.  You can find that link here:

This HOWTO describes how to resolve an issue with vRanger 6.0.1 whereby ALL jobs be it existing or new, incremental or full always fail with the same error: “The database transaction was rolled back” as demonstrated by this sample email log:


There are numerous possible causes for this error.  However, if you are having is for all backups, the most likely cause is your database is full. By default, vRanger 6.0.1 uses SQL 2005 Express MSDE.  Besides being free, it has the baked in limitation that no single database can exceed 4GB in size.  “The database transaction was rolled back” indicates you have maxed out your allocation.  How can you confirm this is your issue?

  • Look under Management / SQL Server Logs / Current.  You should find the following error:


“Could not allocate space for object ‘dbo.SavePointXML’.’PK_Manifest’ in database ‘vRangerPro’ because the ‘PRIMARY’ filegroup is full.”





  • What’s happened here is that vRanger does not automatically delete any activity logs it generates, ever.  Therefore it’s only a matter of time before the 4GB wall is hit. This is documented in this vRanger KB article:


  • The fix is to run a custom SQL script that will purge all of the orphaned data.  But before we do that, let’s verify exactly what the issue is
  • You can review the orphaned data by selecting New Query from SQL Management Studio while connected to SERVERNAME\VRANGERPRO and pasting in the query Get Size of All Tables in a Database at the end of this HOWTO.
  • Copy and paste the results into Excel (or customize the SQL query depending on your preference / skillset) Sort the Database size column from largest to smallest
  • You’ll likely find that the table SavePointXML is at 4GB or full




  • The good news is, you don’t have to clean this up and all of the dependencies on your own.  VisionCore/Quest/Dell has provided a SQL script in the KB article above (also included at the end of this email for reference)
  • Copy and paste Purge Obsolete vRanger Data script at the end of this HOWTO into a new query and run it
  • Note that in my case with the database being full, it took over 45 minutes for the execution of the script to complete and this is without any other backups running so be patient
  • Note: If you get Query completed with errors, check the Messages tab.  If your error message is similar to the one below, it can likely be ignored


  • With the database purged, try running your job again and this time it should be successful


Get Size of All Tables in a Database (found from Google, original author unknown)


Purge Obsolete vRanger Data


    • Andrew G. on April 20, 2015 at 5:37 pm
    • Reply

    This post contains rather old and ineffective script to purge old records. Please use following link to get most recent version:

    1. Thanks Andrew. I’ve posted a link to the link you provided at the top of the article.

Leave a Reply

Your email address will not be published.