You are seeing the below error message on your Sync App, or under your company's Integration Status on the AutoEntry website homepage after logging in.
Connection to the company could not be established. Sage 50 is not installed on this machine, or the libraries required to access Sage 50 company files are not properly installed.
Sage 50 users
This error can be caused by two issues:
Your Sage company filepath is on a C drive, but Sage 50 is not installed on the PC you first installed the Sync App on.
The filepath of your Sage 50 company is on a shared network, but cannot be accessed via the PC you first installed the Sync App on.
Below are the steps required to resolve this error for both instances mentioned above:
1. Sage Filepath is on a Local Network (C Drive)
Check that your Sync App has been installed as a Service application by doing the following:
Open your PC's Task Manager.
Select the Services tab at the top and then click on Open Services at the bottom of that window.
Find AutoEntry.DesktopSync.Service in this new window.
If the start-up type shown here says Automatic, it is a Service Application.
If the start-up type shown here says Disabled, it is a Console Application.
If it is already a Service application, ensure that your Sage 50 application is also installed on the PC you are using to run the Sync App.
2. Sage Filepath is on a Shared Network
If you are seeing this error and your Sage company's filepath is on a shared network, (D, E, S, F drive etc.) you will need to change your Sync App's start-up type to a Console application by doing the following:
Open your PC's Task Manager, select the Services tab at the top, then click on Open Services at the bottom of that window.
When the Services Window opens up:
Right-click on AutoEntry.DesktopSync.Service and select Stop.
Once stopped, right-click on AutoEntry.DesktopSync.Service again and select Properties.
Under Startup Type select Disabled.
Open the Sync App again and ensure you are able to view your company list.
The Sync App is now running as a Console application!
If you are still seeing the error after completing the above steps, please get in touch with our Support team for further guidance.