Sage 50 error: "Could not create cabinet file for accountant's copy
Sage 50 failed to package the accountant's copy, usually because of a disk, path, or company file problem, not your accountant's setup.
When Sage 50 shows “Could not create cabinet file for accountant’s copy.”, it means the program tried to bundle your company data into the compressed transfer file it sends to your accountant, and that packaging step failed. Despite the wording, the problem is almost never on the accountant’s side. It is on the machine creating the copy: the location you are writing to, the permissions on that location, or the condition of the company file itself.
What a “cabinet file” is
An accountant’s copy is a compressed archive containing the portion of your data your accountant needs, plus a dividing date that keeps you both from stepping on each other’s changes. Sage 50 has to build that archive on disk before it can be saved or emailed. “Could not create” means the archive was never successfully written. Your live company data is usually untouched, so this error is annoying rather than catastrophic, but it does block the accountant workflow until it is resolved.
Check where you are saving the copy
The most common cause is the destination. Try saving the accountant’s copy to a simple local folder, such as a new folder directly on your C: drive, rather than a network share, a USB stick, a cloud-synced folder, or a path with special characters. Network drives can drop mid-write, and cloud-sync folders can lock files while they upload, both of which make the archive creation fail. Also confirm the drive actually has free space; a full disk produces exactly this message.
Check permissions and antivirus interference
If you are logged in with a restricted Windows account, or if the folder is read-only, Sage 50 cannot write the archive. Right-click the destination folder and confirm your account has full write permission. Overzealous antivirus software can also quarantine or lock a newly created compressed file mid-write; if you suspect this, try again with real-time scanning briefly paused, or add an exclusion for your Sage data folder.
Try a fresh backup first
A company file that is borderline damaged can fail when Sage 50 tries to read and compress it, even if it opens normally for day-to-day work. Run a full backup of your company, then attempt the accountant’s copy again. If a regular backup also fails or reports errors, that points to damage inside the data itself rather than a destination problem, and the file likely needs professional attention. Our engineers repair damaged Sage 50 and Simply Accounting databases, and we can assess whether the file is the culprit: see our Sage 50 database repair service.
If the file itself is damaged
When the error persists across different folders, drives, and user accounts, the company data is the likely cause. Do not keep retrying on the original, and do not attempt an in-place “repair” by deleting files you find near the company data, since that can make recovery harder. Work from your most recent good backup while the damaged file is examined. If no backup is current, say so when you contact us; recovery from the damaged file itself is often still possible.
A useful next step
Make one fresh backup right now, before anything else, so today’s transactions are protected regardless of the cause. Then send us the file for a free evaluation: we will tell you whether this is a simple environment issue or internal damage, and what the fix involves, with no obligation. You can reach us through our contact page. If you were also planning a move off Sage 50, a failed accountant’s copy is sometimes the moment to consider a Sage 50 to QuickBooks conversion instead, and we can advise on both.