Restore a backup of this company to another directory" Sage 50 message
Sage 50 is telling you the open company file is damaged and it cannot repair it in place; here is what that means.
The message reads, verbatim:
To correct the problem, restore a backup of this company to another directory.
Despite the calm wording, this is Sage 50 telling you that the company file you are working in is damaged, and that the program has given up trying to use or repair it as it stands. The suggested fix, restoring a backup to a different folder, is the software’s way of saying: go back to the last known good copy. It is not offering to fix the current file.
What the message actually means
Sage 50 stores your books in a company database. When that database becomes internally inconsistent, the program refuses to keep working in it, because writing more data into a broken structure risks making things worse. The restore-to-another-directory instruction exists so you do not overwrite anything. Restoring over the top of the damaged file would destroy the only copy our engineers could potentially recover data from.
Why it happens
The usual causes are an interruption while Sage 50 was writing to the file: a power loss, a forced shutdown, a network drop while the file lived on a server or shared drive, or a machine that crashed mid-save. Storage problems and interrupted updates or conversions produce the same result. Sometimes the damage is minor and limited to recent transactions. Sometimes it runs deeper. That depends entirely on the file, and we cannot say without looking at it.
Restore a backup to a new folder
If you have a recent backup, this is the fastest safe path. Restore it into a folder that does not contain the damaged company, so the original stays untouched. You will lose anything entered since the backup was made, so check the backup date before you commit to it. If the gap is a few days of transactions, restoring may be entirely reasonable. If the gap is months, or the backup itself will not restore, read on.
Check for other copies
Before assuming the backup is your only option, look for other recent backups. Sage 50’s own scheduled backups, an off-site copy, or a server snapshot may be newer than the one you first reach for. Compare dates and pick the most recent copy that is not the damaged file itself.
When the file needs professional attention
If there is no backup, the backup fails to restore, or the data gap is too large to accept, the damaged file itself is still worth preserving. Our engineers recover data directly from damaged Sage 50 and Simply Accounting databases, often including the transactions entered after the last backup. Copy the damaged file somewhere safe now, before anything else writes to that drive. Our Sage 50 database repair service starts with a free evaluation, and cost and turnaround depend on what the examination shows.
A useful next step
Stop working in the file, make a copy of it, and send us that copy for a free evaluation. We will tell you what is recoverable, what a repair would involve, and what it would cost, before you commit to anything.