Reconnect the Sage 100 local agent for connection or synchronization issues

You might come to an issue of connection or synchronization with your local agent on your Sage 100 server. There are multiple root causes and possible error messages. Please follow them in order.

Important note:
You should avoid uninstalling and reinstalling the service again, since this action deletes all existing connections and creates additional errors.

Your server is not responding on Spendesk

The first action to perform in this case is to go to Settings > Accounting Setup > Accounting integration and click on the red button Refresh server status. This will try to relaunch the connection with Sage 100 local agent on your server.

Do not click on Switch integration or you will lose all your accounting configuration and installation on your server.

Your local agent needs to be restarted on your Sage 100 server

If the first option did not sort restore the connection, please follow these steps on your Sage 100 server:

Open the Windows Services Management application (service.msc)
Ensure the SAGE100FR service is configured to run under a user account with the necessary access rights to both the Sage SQL database and any network shares where Sage files are stored.
Then, restart the SAGE100FR service.

Your service updater needs to be uninstalled from your Sage 100 server

A third option is also possible if you started using the integration with Sage 100 early on or a few months after Spendesk launched it. On your Sage 100 server you should have a service updater called ChiftServiceUpdater. You can uninstall it or deactivate it on your server. This service causes connection interferences.

Error message 'An error occurred during the initialization of Sage 100 FR. The username is incorrect'

You might see an error message 'An error occurred during the initialization of Sage 100 FR. The username is incorrect' when attempting to export an expense on Spendesk from Bookkeep > Export.

In this case it is an issue of authentication with Sage 100, the Azure user email is incorrect. To resolve this, you need to open your settings.json file located on your server, and modify the value of azureUser with the right email. Make sure it is a proper JSON file modification.

Error message 'Retrieving the COM class factory for component XXX failed' on Sage 100

If you encounter the error message 'Retrieving the COM class factory for component XXX failed', it is caused by a mismatch between the installed Business Objects library and the data available on the computer or server where the local agent is installed. Please check the following in order:

Is the Business Objects library installed?
Is the installed version of the Business Objects library matching the client's Sage version?
Does the installed version of the local agent match the Sage version used by the client?

This error is always due to one of the three points above.

Error message 'Access denied' occurred during the initialization of Sage 100 Business Objects

This error is typically due to the Windows Service running under a user that does not have the necessary permissions.

To resolve this:

Make sure the path entered in the form is correct.
- If the folder is on an external server or network drive, always use the UNC path (e.g., \\SERVER\Folder) instead of a mapped network drive like S:.
Ensure the user running the Windows Service has access to that path.

To change the user for the Windows Service:

Open the Windows Services list.
Find the service named Sage100FRService, right-click on it and select Properties.
Go to the Log On tab, select This account, then click Browse.
In the bottom section, enter the Windows username to use. Click Check Names to verify it exists, then click OK.
Enter the password for that user, and click Apply to save the changes.

Finally, restart the Sage100FRService so the changes take effect. If the issue persists, try using an Administrator account and repeat the steps above.

Error message 'Amazon.Runtime.AmazonServiceException: A WebException with status ConnectFailure'

If you encounter the following error in the logs of the local agent:

Amazon.Runtime.AmazonServiceException: A WebException with status ConnectFailure was thrown. ---> System.Net.WebException: Unable to connect to the remote server --->

This error indicates that the server where the local agent is installed is unable to establish a connection to AWS services, most commonly due to firewall restrictions. Root cause is that the server is blocking outgoing connections to AWS endpoints used by Chift. This typically happens if outbound traffic on port 443 (HTTPS) is restricted at the firewall level.

Diagnosis: Perform a telnet test to check if the required endpoints are accessible from the server:

Open a command prompt on the server where the local agent is installed.
Run the following command:
```
nginxCopyEdittelnet sqs.eu-west-3.amazonaws.com 443
```
- This tests the ability to connect to AWS SQS, which is used for communication between the agent and Chift.
Run a second test for the S3 endpoint (used during large data transfers):
```
nginxCopyEdittelnet s3.eu-west-3.amazonaws.com 443
```

If either test fails (e.g. connection times out or cannot establish), it confirms that the firewall is blocking the connection.

Resolution: Ensure that port 443 is open for outbound HTTPS traffic.

The firewall or proxy should allow connections to at least the following domains:
- sqs.eu-west-3.amazonaws.com
- s3.eu-west-3.amazonaws.com
You may need to allow the full range of AWS IPs for the eu-west-3 region, depending on your network policies. Refer to AWS IP ranges for up-to-date information.

Once the firewall rules are updated and the connection is allowed, the agent should be able to communicate correctly with AWS services and the error will no longer occur.

In case one of these the above options worked out, then you can continue using Sage 100 native integration. Else, you can contact Spendesk customer support using our chatbot, and we will help for troubleshooting.