Skip to main content
🚨 Activation of SAGE 100 requires the support of your IT partner or Sage integrator. All necessary information and assistance are detailed in the pages linked to your version. There are 3 versions for Sage 100 France.
  1. Sage 100 “On Premise”
  2. Sage 100 Azure Sage Partner Cloud (SPC)
  3. Sage 100 Online
👆To continue with setting up the connection, please click on the link corresponding to your version above. Integration with Sage 100 France is only available for Sage 100 “On Premise” and Sage 100 SPC. If you have the Sage 100 Online version and want to set up the integration, it is entirely possible. To do this, you will need to contact Sage 100 in order to upgrade to a Sage 100 “SPC” or “On premise” version.

​
Local agent:

In both versions of Sage 100, “On-Premise” and “SPC”, you will need to install a local agent (program) on the server/computer where your Sage 100 instance is installed in order to establish the connection with the software. To know more about the local agent, here is a dedicated documentation: 📄 Local Agent

​
🚨 If you’re encountering a synchronization error between the Sage 100 FR local agent and Chift:

​
Restart the local agent

  • 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.

​
“Retrieving the COM class factory for component XXX failed”

This issue 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.

​
One folder is connected but others appear inactive or uninstalled

This likely stems from an error during installation: one of the connected folders may have overwritten the existing connections, causing all other previous connections to be lost. To fix this:
  1. Open the settings.json file used by the Windows Service. This file is located at: C://ProgramFiles/Sage100FRService
  2. This file contains the current connections configured in the local agent. In the "connections" section, ensure that there is one connection per entity to be connected to Sage.
Only the currently detected connections will appear in this file. To restore the missing ones:
  • Re-download the connections for the other entities.
  • When the pop-up appears, make sure to select the “add connection” option rather than replacing the existing ones. This will append the new connection to the settings.json file.
Connections should then be restored one by one, as long as you correctly select the option not to overwrite existing connections.

​
An error occurred during the initialization of Sage 100 FR (Objets Metiers)

​
Access denied

This error is typically due to the Windows Service running under a user that does not have the necessary permissions. To resolve this:
  1. 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:.
  2. 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: Amazon.Runtime.AmazonServiceException – Connection failure to AWS services

If you encounter the following error in the logs of the local agent:
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

  • 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.

​
How to diagnose

Perform a telnet test to check if the required endpoints are accessible from the server:
  1. Open a command prompt on the server where the local agent is installed.
  2. Run the following command:
    • This tests the ability to connect to AWS SQS, which is used for communication between the agent and Chift.
  3. Run a second test for the S3 endpoint (used during large data transfers):
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.