Sage 50 "company database could not be found, or the database engine is not running
Sage 50 cannot reach the database behind your company file, so the transaction is refused until the connection is restored.
The message reads:
This transaction could not be processed because the company database could not be found, or the database engine is not running.
Despite the wording, Sage 50 is not saying your transaction is bad. It is saying the program lost contact with the database that sits behind your company data. Sage 50 stores your books in a database managed by a separate engine process, and when that engine stops, or the program cannot find the database, every save is refused. The transaction itself is usually fine; the connection is the problem.
Why the connection drops
The most common triggers are mundane. The database engine service did not start when the machine booted, or it stopped after a Windows update or a crash. On a networked setup, the machine hosting the data went offline, was renamed, or its shared folder became unreachable. Less often, the database files themselves are damaged, and the engine refuses to load them.
Check the engine first
Restart the computer running the company data. That restarts the database engine in the correct order, which resolves a surprising share of cases. If you are on a network, restart the host machine first, wait for it to fully load, then restart the workstation. Do not skip waiting; the engine needs time to come up before workstations connect.
Check the path and the host
If the error persists, confirm the workstation is still pointing at the right place. Open your company the way you normally do and look at where the data is being opened from. A renamed computer, a changed share, or a remapped drive breaks the link even though nothing is wrong with the data. Reopen the company by browsing to its actual location rather than relying on a recent-files entry.
Try a backup restore if the data will not open
If the company will not open at all, and the engine is definitely running, the database files may be damaged. Restore your most recent backup to a new folder and open that copy. You will lose anything entered since the backup, so keep the damaged original untouched; it may still be recoverable.
When the file needs professional attention
If the engine runs, the path is correct, and the database still will not load, the data files themselves are likely damaged. Repeated restore attempts and third-party repair tools can make this worse. Our engineers repair damaged Sage 50 and Simply Accounting databases directly, and we can tell you quickly whether yours is recoverable. See our Sage 50 database repair service for what that involves, or contact us about your file for a free evaluation and a no-obligation quote.
If you were already considering moving this data to QuickBooks, a damaged database does not rule that out; our Sage 50 to QuickBooks conversion can often work from the same files once they are stabilized.