Sage 50: "An error occurred while reading the file that you selected.
Sage 50 found the file you picked but could not read its contents, which usually points to a wrong selection, a bad copy, or real damage.
When Sage 50 shows “An error occurred while reading the file that you selected.”, the program located the file you pointed it at but could not read what is inside. “Reading” is literal: Sage got far enough to open the file and then failed to make sense of its contents. Despite how it sounds, the cause is often not damage. Frequently the wrong file was selected, the copy is incomplete, or part of the company’s data is missing; only sometimes is the file itself corrupt.
Confirm you selected the right file
Sage 50 stores companies differently by edition, and mixing up the pieces is the most common trigger for this message:
- In the Canadian product (sold as Simply Accounting), each company is a .sai company file sitting beside a matching .sj data folder. The two must share a name and a location. Selecting the .sai when its folder is missing, or pointing Sage at the folder alone, will fail.
- In the US product (Peachtree), a company is a whole folder of data files, not a single file. A partial copy of that folder reads as a broken company.
- Backups cannot be opened as companies. A backup archive has to be restored first (commonly .ptb in the US product, .cab in the Canadian one, depending on release), using the restore option rather than the open one.
- A desktop shortcut or recent-files entry may point at a folder that was moved, renamed, or restored to a different path.
Check the copy, not just the original
If the file reached this machine by copy, suspect the copy:
- A file copied while the company was still open in Sage is internally inconsistent.
- Cloud-sync folders, email attachments, and interrupted USB transfers can truncate a file or drop parts of a data folder. Compare the copy against the source, and confirm every file in the company came across.
- If the company lives on a server share, copy all of it (the .sai and its .sj folder, or the entire company folder) to a local drive and try there before assuming damage. Permission changes and antivirus quarantine produce this same message.
Restore a backup instead
If you have backups, restore the most recent one to a fresh folder rather than over the existing company. If that backup also fails to read, try an older one: several dates failing the same way means the problem is older than you think, or the disk itself is failing.
Use Sage 50’s built-in repair
Sage 50 includes a maintenance utility, File Maintenance, with a Check Data step that reports problems and a Repair Data step that fixes many of them. Where it lives depends on your release and edition, so look for it among the maintenance options rather than assuming a fixed menu location. Run Check Data on a copy first, note what it reports, then run Repair Data. Repair rewrites data, so keep the original untouched. If Check Data finds errors that Repair Data cannot clear, or the message persists after a repair, the built-in tool has reached its limit.
When the data itself is damaged
Real damage comes from an interrupted write (power loss mid-save), a failing drive, or a backup made from an already-bad file. If two or more backups fail the same way, the file needs professional attention: no setting, reinstall, or retry fixes bytes that are wrong inside the file. Our engineers repair damaged Sage 50 and Simply Accounting databases at the data level, and if you met this message while moving to QuickBooks, the Sage file must be readable before any conversion can succeed.
Work through the steps in order: verify the selection, recopy with Sage closed, restore a known-good backup, then Check Data and Repair Data on a copy. If the error survives all four, stop retrying, because repeated attempts on a failing disk make recovery harder. Get the file looked at: we provide a free evaluation and will tell you what is recoverable before you decide anything.