Sage 50 · 3 min read · Updated August 13, 2026

You cannot backup a company while you are in read only mode" — Sage 50

Sage 50 is refusing to create a backup because your company file is open in read-only mode, which blocks all write operations.


Sage 50 is telling you that the company file you have open is marked read-only, and because a backup writes a new copy of the file to disk, the software cannot complete the operation. The message is straightforward in this case — it is not masking a deeper corruption issue — but the reason your file landed in read-only mode can vary.

“You cannot backup a company while you are in read only mode.”

When Sage 50 opens a company in read-only mode, it treats the data as locked: you can view, print, and report on it, but nothing can be written — not new transactions, not edits, and not backups. The backup command is treated as a write operation because it creates and saves a new archive file.

Close and reopen the company normally

The most common cause is that the company was opened with a read-only flag selected on the open-company dialog, or the file was opened from a copied or restored location that carries read-only attributes. Close the company completely, then reopen it from its proper folder without selecting any read-only option. If the option persists, check the folder permissions on the directory where the company data lives — if the Windows user account does not have full read-write access to that folder, Sage 50 may default to read-only.

Check whether another user or workstation holds a lock

On multi-user Sage 50 installations, a company can open in read-only mode if another workstation has an exclusive lock on the data, or if a previous session crashed and left behind a lock file that was never cleaned up. Restarting the machine that hosts the shared company data, then reopening the file locally on that machine, often clears stale locks.

Copy the file to a local folder and work from there

If the company lives on a network share, a mapped drive, or external media, Windows may be applying read-only attributes that Sage 50 respects. Copy the entire company folder to a local directory on your workstation (such as your Documents folder), remove the read-only attribute from all files in the copy, and open that local copy. If the backup succeeds there, the problem is network or folder permissions, not the data itself.

If the file is damaged and will not open normally

Sometimes a company file will only open in read-only mode because Sage 50 detected a structural problem and is protecting the data from further changes. In that situation, the read-only restriction is a symptom of file damage rather than a settings issue, and the backup command will remain blocked until the underlying file is repaired. Our engineers regularly handle Sage 50 and Simply Accounting database repair for files in exactly this state.

If none of the steps above clears the read-only condition, the safest next step is to send us the file for a free evaluation — we can determine quickly whether it is a permissions problem or something structural, and give you a clear quote before any work begins.