Error: "The file does not contain any backups..." when restoring a SQL database

Alerts and notices
Leave feedback

Internal Employees: Submit feedback

Contact information (optional):

Leave this blank:

Please tell us how we can make this information more helpful.


Characters left:

When attempting to restore a SQL database you receive the following error: "The file does not contain any backups, access is denied on the file, or the path does not exist. Please select another location and try again.".

This error is generated if you attempt to restore a database created in a newer version of SQL (for example, if you attempt to restore a 2014 SQL database into a 2012 SQL instance). To resolve this, you need to install the same or newer version of SQL as the backup.

What version of SQL is the backup from?

If the backup came from Virtual Office CS/SaaS, contact Support at 800.968.0600 to find out the version. You need to know the Firm ID of the Virtual Office CS/SaaS firm the data came from.

If the backup came from a non-Virtual Office CS/SaaS installation, such as a local, LAN, Terminal Server, or third-party cloud installation, you need to check the version of SQL installed on the machine the backup was made from.

Install the matching or newer version of SQL

  1. On the machine you want to restore the backup to, install the matching or newer version of SQL you found in the section above. To download and install SQL, consult your firm's IT professional. 
  2. After completing the SQL installation, run the installation for the CS program you are restoring backup data for (Accounting CS, Workpapers CS, FileCabinet CS, or Practice CS). Skip to step 2 of the installation and either choose an existing instance of SQL, or choose to create a new instance. 
  3. After completing the CS installation, attempt to restore the backup within the CS program.

Internal notes


How to install/use a newer version of SQL on your own machine:

If you need to restore a firm's data to your machine for testing, you will need to install the version of SQL the database came from.

  1. Install the necessary version of SQL. You do not need to uninstall the version of SQL you currently have because you are able to use multiple versions of SQL on one machine. You can follow the instructions to install a new instance at the bottom of Upgrading to or installing a Microsoft SQL 2012 instance.

    Note: When entering the instance name during the installation, it is a good idea to use the SQL version number in the name. Since you will have multiple instances, this will make it easier to tell the difference between them.

  2. In order to be able to use multiple instances of SQL, you will need to modify datasource.xml and reference the correct instance between <server><\server>. There are a few ways to do this.
    • You can type the instance name in the datasource.xml each time you want to switch.
    • You can have two lines of <server></server> in a single datasource.xml. The instance name you are not using will be renamed. Each time you want to switch, you will open datasource.xml and switch the instances within the file. 
    • You can have multiple versions of datasource.xml. For example, if you want to use SQL 2012, you will have a datasource.xml file with the 2012 instance listed. You will also have a datasource.xml.2008 with the SQL 2008 instance listed. To switch back to 2012, rename datasource.xml to datasource.xml.2012. Then rename datasource.xml.2008 to datasource.xml.

Share This