Factorial - Sage 100 France | Employees: Troubleshooting

Factorial - Sage 100 France | Employees: Troubleshooting

📘 Setting up Factorial - Sage 100 France? Follow the complete step-by-step guide: Setup an automated data interface between Factorial and Sage.

Something not working with the Factorial - Sage 100 France Employees interface? Start with the three quick checks below. They solve or explain most problems. Then look up your situation in the table.

New to this interface? See the full setup guide first.

Start here: three quick checks

✅ Check 1: what does the run log in BrynQ say? Open the interface in BrynQ, go to Runs and open the latest run. Messages that start with ⚠️ ACTION REQUIRED say what went wrong and what to do. The run log also shows what was found and sent. Always start here: most problems are in the data or the interface setup, not on the Sage server.
✅ Check 2: are the three BrynQ services running? On the Windows server, open Task Manager > Services (see The Agent services are not running).
✅ Check 3: what do the Agent log files say? On the Windows server, open C:\ProgramData\BrynQ\Agent\logs (see Find the Agent log files).
💡 Checks 2 and 3 in one place: open the admin page http://127.0.0.1:7071/admin on the Windows server and go to SAGE 100 France > Troubleshooting (see The admin page: SAGE 100 France › Troubleshooting).

Find your problem

What you see📍 Where to fix itWhat to do
'Erreur mot de passe' on the Sage server (this happens often)Sage 100 FranceCheck the code and token of the Sage service account first, then reinitialise the user or the dossier. See Fix 'Erreur mot de passe'.
BrynQ cannot reach the AgentWindows server, then BrynQCheck the three BrynQ services, open http://127.0.0.1:7071/admin on the Windows server and go to BrynQ connection: both This agent signs in to BrynQ and BrynQ reaches this agent must be OK (click Test again). Then test the Sage authorization again from the Authorization tab.
Not all employees are syncedBrynQ (run log), then Factorial or the interface setupRead the run log first. Common causes: the Factorial user cannot see all employees (permissions), missing or wrong data in Factorial, a value mapping that is not filled in, or test employee IDs still in the Configuration tab. See Employees are missing or nothing is imported.
No import file appears on the serverBrynQ (run log), then the Windows serverRead the run log first. No file is sent when the interface found no new or changed employees to send: that can be normal, or a sign that all employees were filtered out (permissions, data, value mappings; see Employees are missing or nothing is imported). Does the run log say a file was sent? Then BrynQ could not deliver it to the Agent: check the services and the logs\agent files.
Import file is there, but Sage has no or wrong recordsBrynQ (run log and Scenarios tab), FactorialCheck the run log, the data in Factorial and the value mappings, especially 'Legal Entity -> Paying Establishment and Dossier' in the scenario Registration, and the logs\sage files.
Parts of the installation fail, or the Agent runs but cannot read or write filesWindows serverCheck the Windows permissions. See Installation or file access fails.
Installer: Next stays unavailable on Cloud connectionWindows server (installer), then BrynQBrynQ does not accept the token yet. The page says why: copy the whole token, add the public IP address of the server to the token in BrynQ, or use the agent token of this customer. Then click Check again.
Installer: Next stays unavailable on Sage import modelsSage 100 France, then the installerA model is not found yet, or Sage is still open. Select the row with the red cross to see what to do, and close Sage (all sessions) once all three models are found. See Step 5 of the full setup guide.
The installer cannot connect to SQL ServerWindows server (installer)See The installer cannot connect to SQL Server.
An app used by the template is inactiveBrynQActivate it in Settings > Interfaces > Apps.
A manual Sage import works, but the automated run does notWindows server, then BrynQCheck the Agent on the admin page (http://127.0.0.1:7071/admin) under SAGE 100 France > Overview and Troubleshooting, then test the Sage authorization again from the Authorization tab.
You need to review or remove an authorizationBrynQOpen Settings > Interfaces > Connections.
Anything else you can't explainWindows serverDownload the support file and send it to BrynQ support. See Contacting BrynQ support.

The Agent services are not running

📍 Where: the Windows server.

  1. Open Task Manager and go to the Services tab.
  2. Check that all three BrynQ services have the status Running.

  3. Is a service stopped? Right-click it and choose Start. Wait a moment and check that the status changes to Running.
  4. Does it not start, or does it stop again? Contact BrynQ support with a screenshot of the Services tab and the support file (see Contacting BrynQ support).

The admin page shows the same: SAGE 100 France > Troubleshooting > Are the BrynQ services running?, with an Open Services button.

The admin page: SAGE 100 France › Troubleshooting

📍 Where: the Windows server, in a browser (Edge, Chrome or Firefox).

  1. Open http://127.0.0.1:7071/admin (or use the desktop shortcut BrynQ Agent). The page only opens on the server itself.
  2. Go to SAGE 100 France and open the tab Troubleshooting.
  3. Check Are the BrynQ services running? and What do the log files say? (tabs Sage import, Sage ConnectImport and BrynQ Agent; newest first, click a file to read it).
  4. Under Find your problem, click a problem to see the steps.
  5. Need BrynQ support? Click Download support file and attach the file to your ticket.

15-sage-troubleshooting

The main Troubleshooting page in the menu also checks the connection with BrynQ, folder access, the public IP address and the outbound connections.

Find the Agent log files

📍 Where: the Windows server, in File Explorer.
The log files usually tell you (and BrynQ support) what went wrong. Which folder you need depends on the problem:

ProblemLog folder
Importing data into Sage fails or gives wrong resultsC:\ProgramData\BrynQ\Agent\logs\sage
General Agent issues, such as connection problemsC:\ProgramData\BrynQ\Agent\logs\agent

Sage import logs (for example connectimport and connectimport-error):

General Agent logs (for example application, requests and security):

You can also read these files on the admin page (see above).

Can't see the ProgramData folder? It is hidden by default. Type C:\ProgramData\BrynQ\Agent\logs directly into the File Explorer address bar.

Fix 'Erreur mot de passe'

📍 Where: Sage 100 France, on the Windows server.
The error 'Erreur mot de passe' occurs quite often on the Sage server. It has two common causes:

  • The code or token of the Sage service account that the BrynQ import uses is not correct, or the token is no longer active. This is the likely cause when no import with this account has worked yet, or after someone changed the account in Sage.
  • Sage still holds an old session of the account. This is the likely cause when imports worked before. Reinitialise the user or the dossier (options A and B).

The admin page names the likely cause: open http://127.0.0.1:7071/admin > SAGE 100 France > Troubleshooting and read the latest import message.

Check the service account first

  1. In Sage, go to Fichier > Droits d'accès > Utilisateurs and open the service account of the BrynQ import.
  2. Check that Mode d'authentification is Compte de service and that Token actif is ticked. Note the Code.
  3. Not sure the token is right? Click Générer for a new token, copy it and click OK.
  4. On the Windows server, open http://127.0.0.1:7071/admin > SAGE 100 France > Service. Check that Sage user code matches the Code in Sage. If you generated a new token, click Replace token, paste it and save.
  5. Wait for the next import cycle (15 minutes by default) and check the import message again.

Still 'Erreur mot de passe'? Reinitialise the session. Start with option A. Only use option B if A does not help.

Option A: reinitialise from within the company (try this first)

  1. Open Sage 100 France and connect to the company (PRH file).
  2. Go to Fichier > Droits d'accès > Utilisateurs.
  3. In the Liste des utilisateurs, click Réinitialisation.
  4. Try the connection again.

Option B: global reinitialisation of the dossier (use at your own risk)

⚠ At your own risk. Réinitialiser le dossier signs out all users of the dossier. Make sure nobody is working in payroll before you use it.
  1. Go to Fichier > Utilitaires > Réinitialisation.
    Don't see it? This option is sometimes only visible when you are not connected to a company. Close the company first (Fichier > Fermer) and look again.
  2. The Assistant réinitialisation de dossier opens. Click Parcourir... and select the dossier (PRH file) to reinitialise.
  3. Click Réinitialiser le dossier. To sign out one specific user only, select that user and click Réinitialiser l'utilisateur instead.
  4. Click Terminer and try the connection again.

Installation or file access fails

📍 Where: the Windows server.
The most common cause is missing Windows permissions. This does not always show a clear error.

  • Run the installer with a Windows account that has administrator rights on the server (right-click the installer and choose Run as administrator).
  • Make sure the Windows account the Agent runs under can read and write the Sage folders and PRH files, and the programFiles and programData folders.
  • The installer stops with a message that a BrynQ folder was created by another user? Run the takeown command the message names, then run the installer again.
  • The installer keeps a copy of its log in C:\ProgramData\BrynQ\Agent\logs\installer (setup-<date>-<time>.log). Look for Access is denied.
  • Fixed the permissions? Run the installer again, then check that the three BrynQ services are running.

The installer cannot connect to SQL Server

📍 Where: the Windows server (installer).

  • Click Test connection: it shows Connection successful, or the reason why it failed.
  • Login method: choose Windows authentication or SQL Server authentication (username and password). If SQL Server refuses the login, the message tells you which one to try.
  • Server name: check that the SQL Server suggested by the installer is the one that holds the Sage databases. Not sure? Open SQL Server Management Studio: the Server name field in the "Connect to Server" window shows the right name. Or ask your IT administrator.
  • ODBC driver (under Advanced...): choose the driver with the highest number, for example ODBC Driver 18 for SQL Server. To see what is installed, search Windows for ODBC Data Sources (64-bit) and open the Drivers tab.
  • Database access: the account used to connect (your Windows account, or the SQL Server login) must have access to the Sage company databases.

Employees are missing or nothing is imported

📍 Where: BrynQ (run log, Configuration, Scenarios and Authorization tabs) and Factorial.

Start with the run log of the latest run (interface > Runs). It shows what BrynQ found and sent, and the messages about employees that were left out. Then check these causes, in this order:

  1. Test employee IDs. Did you enter employee IDs in the Configuration tab? Then only those employees are processed. Remove them when you are done testing.
  2. Factorial permissions. BrynQ only syncs the employees that the connected Factorial user can see. Reconnect the Factorial authorization with an administrator account. Watch out: if you are already signed in to Factorial in your browser, Connect to app connects straight away with that account. Sign out of Factorial first, or use a private/incognito window.
  3. Data in Factorial. Missing or wrong data can leave employees out, for example a matricule that is not exactly 4 characters. The run log and the reports show which employees and fields are affected.
  4. Interface setup. A value mapping that is not filled in leaves the employees with that value out. Check every item with an exclamation mark (!) in the Scenarios tab, and especially 'Legal Entity -> Paying Establishment and Dossier' in the scenario Registration: a legal entity without a Sage company is not sent.
  5. Nothing new to send. BrynQ only sends new and changed employees. When nothing changed in Factorial since the last run, no file is sent. That is normal.
💡 Get the reports by email. Set the variable Send Report to to your email address to receive the reports of each run, such as the values without a mapping and the records that were left out. Set Enable Data Validation to true for a report with the fill rate of each field.

Contacting BrynQ support

Help us help you faster. Include:

  • A short description of what you did and what you see (a screenshot of the error helps).
  • The support file: on the admin page, SAGE 100 France > Troubleshooting > Download support file. It holds the logs, the settings and the status of the services in one zip file, with passwords and tokens left out. Admin page does not open? Run "C:\Program Files\BrynQ\Agent\brynq-agent.exe" --support-file in a Command Prompt as administrator; the file is saved on your Desktop.
  • The name of the interface in BrynQ.