| | Error: 'The database engine reported an error...' |
| Cause | - The data file is still open by Sage 50 (or a third-party program)
- The Connection Manager has stopped working
- The SAJ folder contains unwanted files
- Antivirus is blocking Sage 50
- One of the users has already converted the data file to a higher version
|
| Resolution | When opening a data file in 2026 - Go to Windows Start, open the Control Panel and select Programs and Features.
- Locate Microsoft Visual C++ 2015-2022 Redistributable (x64) from the list. Right-click on it and click Change/Repair.
- Follow the Wizard to complete the repair process.
- Repeat the steps for the Microsoft Visual C++ 2015-2022 Redistributable (x86).
- Reopen Sage 50.
When opening a 2026 data file in 2025 - Install version 2026.
- Make sure all users have installed version 2026. This includes users on Remote Data Access.
Restart the Connection Manager - Restart Connection Manager.
- Open the file again and verify that there's no error message.
Move the data to a new folder - Move the SAI file and SAJ folder to the C:\\.
- Open the file from there.
- Ensure the file isn’t on OneDrive, Google Drive or other cloud services.
- Verify that the file opens.
Check the SAJ folder - Ensure the SAJ folder is clean of unwanted items.
- Open the file again.
The file is on Remote Data Access - Select Connect to a shared company from the Sage 50 Welcome screen.
- If you don't have another company file to open, open the sample company
- Go to File, then Connect to a Shared Company
- If prompted, log in with your Sage account email address.
- Select the company file having the issue and click Download.
- Choose the location and file name and click Save.
- If you wish to overwrite the existing file, select the same name and location and click Yes.
- Verify the data opens normally.
The file is on the Network Follow the steps to resolve the error: "Database engine has reported an error" in a network environment. End MySQL task - Close Sage 50 on all the computers.
- Open Windows Task Manager of the computer hosting the database.
- Select the Process tab.
- Check the Show processes from all users button.
- End any mysqld.exe (or mysqld-nt.exe) from the Image Name list.
- Open your data file again.
|
|