Your data may have been corrupted by an unfinished process" (Sage 50)
Sage 50 is warning that a task was interrupted before it finished writing, so the company file may be incomplete or damaged.
Sage 50 is telling you that something it was doing with your company file did not finish cleanly, and as a result the file may not be in a consistent state. The exact wording, “Your data may have been corrupted by an unfinished process,” sounds alarming, but “may” is doing a lot of work here: the program often shows this message as a precaution when it cannot confirm that a previous operation completed, not because it has positively detected damage.
What the message actually means
Sage 50 writes to your company file in steps. If a process is cut short partway through, by a crash, a power loss, a forced shutdown, a network drop while the file is on a shared drive, or closing the program before a save or backup finishes, the file can end up with some changes written and others not. When Sage 50 next opens the file and sees that unfinished work, it raises this warning. The file might be genuinely damaged, or it might be fine apart from the last few transactions, and the program cannot tell which without checking.
Restore from a backup first
The safest response is not to repair the file at all: restore your most recent backup from before the interruption. A clean backup sidesteps the question of what the unfinished process left behind. You lose whatever was entered after the backup, which is usually a small, known amount, and you get certainty instead of a repaired-but-suspect file. If you use Sage 50’s built-in backup routine, restore to a new location rather than over the existing file so you keep both.
Let Sage 50 check and repair the file
If there is no usable backup, let the program run its own data-checking and repair routine on the file. Sage 50 includes integrity checking that can find and often fix inconsistencies left by an interrupted write. Make a copy of the company file before you start, so that if the check or repair itself fails partway, you still have the original to work from. Work on the copy, never the only copy.
Look for the interruption’s cause
It is worth identifying why the process was unfinished, because the same cause will do it again. Common culprits are a workstation losing its network connection to a hosted file, the machine going to sleep or restarting mid-save, a power event, or someone ending the Sage 50 task from the task manager because it seemed hung. If the file lives on a network share or a hosted server, check that connection stability before trusting the file to daily use again.
When the file needs professional attention
If the backup route is not available and Sage 50’s own check fails, stalls, or reports errors it cannot fix, the file likely has structural damage inside the database, and repeated repair attempts on a damaged copy can make recovery harder. At that point the file should be looked at by a repair service rather than worked on further. Our engineers handle damaged Sage 50 and Simply Accounting databases directly, and if you are considering moving away from the file entirely, we also handle Sage 50 to QuickBooks conversions from files in this state.
Next step
Stop entering data into the file, make a safe copy of it as it stands now, and then decide between restoring a backup and having the file evaluated. We offer a free evaluation of damaged Sage 50 company files, so if the built-in check does not resolve the warning, send us the copy and we will tell you what is recoverable before you commit to anything.