Sage 50 error: "Accounting cannot verify the integrity of the backup file.
Sage 50 checked your backup before restoring it and found it incomplete or damaged, so it refused the restore to protect your data.
“Accounting cannot verify the integrity of the backup file.” is what Sage 50 says when it inspects a backup before restoring it and does not like what it finds. The backup is incomplete, damaged, or a faithful copy of a company file that was already damaged when the backup was made. It is a safety check refusing to proceed, not a verdict that your books are wrong, and in most cases the underlying data is still recoverable.
Why it happens
Backups fail this check for a handful of recurring reasons:
- The backup was interrupted partway through: a dropped network connection, a destination drive that filled up, or the program being closed before the backup finished writing.
- The backup file was copied to or from a USB key, network share, or cloud sync folder, and the copy came up short or was altered in transit.
- The company file was already damaged when the backup was created, so the backup preserves the damage perfectly and fails the same check on every machine.
- The backup was made in a newer release of Sage 50 than the one now trying to restore it. Older releases generally cannot read backups produced by newer ones, and the failure can surface as this message rather than a clearer one.
What to try first
Work through these in order, safest first:
- Try a different copy. If a second copy exists anywhere, another drive, an email attachment, a cloud folder, another machine, try that one before anything else.
- Copy it local. Move the backup onto the local hard drive and restore from there rather than from removable media or across the network. Interrupted reads from those sources are a common cause of this failure.
- Compare sizes. If you know roughly how big the backup was when it was made, check. A copy that is dramatically smaller was cut off in transit.
- Match the release. If the backup came from a computer running a newer release of Sage 50, restore it there, or on a machine with the same or newer release, before assuming the file itself is bad.
- Protect what you have. Do not delete anything, and do not let anything overwrite the drive the backup sits on, until one copy restores cleanly.
If every copy fails
When a second or third copy fails the same way, the problem is usually upstream: the company file was damaged before any of those backups were taken. Damage to the backup container does not mean the data is gone. Our engineers take failed backups apart, validate the pieces individually, and rebuild a working company file from what survives. How much comes back depends entirely on the file, which is why we evaluate before recommending anything. This is the kind of work covered by our Sage 50 and Simply Accounting database repair service.
What not to do
- Do not rename the backup, and do not open and re-save it in other software. Both can overwrite the exact parts a recovery works from.
- Do not keep re-running the restore hoping for a different result. The check reads the same bytes every time.
- Do not run cleanup or repair utilities on the drive holding the only copy.
Next step
If the only backup you have is the one failing, stop attempting restores and get an evaluation instead. Use our contact page to send the file, or a copy of it, and ask for a free evaluation: we will tell you in plain terms what is recoverable, and any quote comes after that, with no obligation. Until you hear back, keep the failed backup somewhere safe and untouched, and keep at least one copy of it on separate media.