An error has occurred during the save of the report" in Sage 50
Sage 50 could not write a report to disk, usually because of a save-location problem or a damaged company file.
Sage 50 is telling you, in vague wording, that it failed to write a report out of the program. The message reads:
An error has occurred during the save of the report.
It appears when you export, print to file, or save a report to PDF or another format. Sage 50 does not say what went wrong, so the real cause has to be worked through in order of likelihood.
What the message means
The report itself was generated fine. The failure happened at the last step, when Sage 50 tried to hand the finished report to the printer driver, PDF writer, or export destination. So the problem is almost always in the destination, not in your data. In a minority of cases, though, the company file is damaged enough that the report cannot be finalized, and the save fails as a side effect.
Save to a different location first
The safest check is to change where the report goes. Save to your local desktop instead of a network drive, a mapped folder, or a folder synchronized by a cloud service. If the desktop save works, the original destination is the problem: it may be offline, full, read-only, or blocked by folder permissions. Cloud-sync folders in particular can lock a file mid-write.
Check the PDF or printer driver
If the failure happens when saving as PDF, the PDF component Sage 50 relies on may be misconfigured or out of date. Try printing the same report to a physical printer, or to a different PDF printer if you have one. If another output works, reinstalling or repairing the PDF printer driver usually resolves it. We cannot say which driver your installation uses, as that depends on your version and setup.
Try a different report
Run a small, simple report, such as a trial balance for one month, and save it the same way. If small reports save but large ones fail, the file may be oversized or the report content may be triggering a fault. If every report fails regardless of size, the destination is the more likely culprit.
When the company file is the cause
If saving fails for every report and every destination, the data itself may be damaged. A company file with corrupted tables or a broken index can fail exactly here, at the point the report is finalized for output. Back up the file first, then restore that backup to a test location and try the same report. If the restored copy behaves the same way, the file needs professional attention rather than repeated retrying.
Our engineers repair damaged Sage 50 and Simply Accounting databases, and we can tell you quickly whether the fault is in the file or somewhere else. You can send us the file for a free evaluation of your Sage 50 database, with no obligation. If the report problem turns out to be a symptom of deeper damage, we will quote the repair before any work starts.