For many of those working with Sage 50, you may have run into the issue where the Sage 50 client is unable to open the company file spitting out an error message along the lines of “database engine reported an error”.
There are a few things to check, as reported and suggested by Sage on their knowledge base at https://support.na.sage.com/selfservice/viewContent.do;jsessionid=F53FE8F7390F7C1308A9800A8386F5E7.worker1d?externalId=11112.
- Verify that the SAJ folder is not read-only
- Verify all files and folders in the SAJ folder are visible
- Restart the Sage 50 Connection Manager
- Re-install the client
- Repair or re-install the .NET framework
- Verify the MySQL daemons exist and are running
- Data is not encrypted or zipped
- Restart the server
- Check the event logs
Instead of running to the event logs as initially thought, we had run through this list as per Sage Phone Support as previous version of Sage 50 have not written event logs.
The first real piece of information in the event logs were Event ID 100 with a source of MySQL under Application.
“Can’t create test file D:\File Shares\Data\Sage Company Files\Company.SAJ\server.lower-test
For more information, see Help and Support Center at http://www.mysql.com.”
This error message is an indication that it does not have access to the SAJ folder to modify/create data. The first two suggestions above have knocked out the possibility of the users not having access. We began by checking the service for MySQL, and verified the user account that service is running under; which happened to be the local system account. Checking the security permissions of the company folder it was found that the System account does not have access to the folder. By providing the SYSTEM account full access to the contents the Sage 50 client was able to connect to the company file and log in.