Sage 50 "Failed to save a local copy of the database" fix
Sage 50 cannot write its working copy of your cloud-hosted company file to this computer, so the file will not open.
You are seeing this message:
CollaborationUIController::OpenCloudData(), Failed to save a local copy of the database.
Despite the technical wording, this is not a database error in the accounting sense. Sage 50 is trying to open a company file stored in the cloud, and part of that process is saving a local working copy of the file onto your computer. That save failed. The program is telling you the download or the write to disk did not complete, not that your bookkeeping data is necessarily damaged.
Why the local copy matters
When a company file lives in cloud storage, Sage 50 does not work directly on the remote copy. It pulls the file down, writes it to a working location on your machine, and opens that. If the download is interrupted, or the destination is full, read-only, or blocked by security software, the local save fails and you get this message before the file ever opens.
Check the obvious first
Start with the simple causes. Confirm your internet connection is stable, and that you have enough free space on the drive where Sage 50 keeps its working files. Restart the machine and try opening the company again. If another user has the same file open in a multi-user setup, wait until they close it, since a locked file cannot be copied down cleanly.
Permissions and security software
The folder Sage 50 writes its local copy into needs full read and write permission for your Windows user. Corporate machines, roaming profiles, and aggressive antivirus policies are common culprits. Temporarily pausing the antivirus, or asking your IT person to allow that folder, often resolves it. We cannot give an exact folder path here because the location depends on your Sage 50 version and how it was installed.
When the cloud copy itself is the problem
If the local side checks out, the cloud copy may be the issue. A file that was uploaded incompletely, or a sync that stopped partway, can fail to download no matter what you do locally. Restoring a known-good backup of the company file to the cloud location, if you have one, is the safest next step. Do not keep retrying against a partially synced file, and do not delete the cloud copy to “start fresh” unless you have a backup elsewhere first.
If the file may be damaged
Sometimes the local save fails because the company file itself is damaged in a way that surfaces during the copy. In that case no amount of reconnecting or restarting will help. Our engineers repair damaged Sage 50 and Simply Accounting databases directly, and we can tell you quickly whether the problem is the connection or the file. If you would rather move off Sage 50 entirely, we also convert Sage 50 data to QuickBooks. Either way, start with a free evaluation: send us the file through our Sage 50 database repair service page and we will assess it at no cost, with a quote for the actual work before anything is done.