Is Winbooks installed on a network drive or the data hosted on a network drive

1. Update the settings.json to map your network drive with a UNC path

If the user is using a network drive, some changes needs to be done in the settings.json to be able to have the connection running properly.

You will first need to be find the UNC path of your network drive.

For example if you are using the P:// drive, this is most likely a network drive so you'll need to get the UNC path for that drive. It will look like something like this: \\chi-win02\sage_compta

You will then need to update the value of the settings.json to be able to let the agent know how to handle this P:// path. For this, you will find two values in the Json: toReplace and replaceWith. The values will by default be set to null

The idea is thus to change the values provided for those fields and to fill in the values that you got just before.

You will then end up with the following elements in the settings.json

"toReplace": "P://" , "replaceWith": "\\\\chi-win02\\sage_compta"

Note that in this json file, all \ need to be doubled (here in my example, \\chi-win02\sage_compta became \\\\chi-win02\\sage_compta)

2. Make sure that the user that is running the service has access to both Winbooks and the network drive

Open the service tab of your windows server by searching with the service keyword on your server.

Open it and search for the service named WinbooksService.

You need to perform a right click on this service, click on the properties option.

You will need to use the this account section and select a user that has access to both the network drive and the folder into which all winbooks files are stored.

3. Once all the checks before have been completed, restart the service and test the connection

Restart the local agent

• Navigate to the service.msc windows app

  

• Make sure that service is configured with a windows user with access privileges to SQL DB and network shared drives

  

• Then restart the winbooks service

  

Errors related to VFPOLEDB on the log.html file

• Navigate to the Winbooks service folder “C:/Program Files (x86)/WinbooksService/” and launch the “VFPOLEDBSetup” executable

  

• Uninstall it (windows admin privileges required)

  

• Then launch the installer again (windows admin privileges required)

  

• Don’t check the “Sample data files and programs” checkbox

  

• Make sure that “Everyone” option is checked, otherwise the driver won’t work with the local system user executing the Winbooks service.

  

• Proceed with installation

  

• Navigate to the service.msc windows app

  

• Make sure that service is configured with a windows user with access privileges to SQL DB and network shared drives

  

• Then restart the winbooks service

  

The given company doesn't exist in the accounting system

This means that we are not able to find the accounting folder. This is often due to the connector not being able to find the path where the data is stored. Either due to access rights issues or network drives access issues.

1. Check the path configured in the Winbooks connection form on Chift

   • Make sure the specified path (e.g., C:\\Winbooks) exists.

   • Verify that this folder contains the Winbooks.ini file.

   • ⚠ If the path does not exist or is not accessible by the user running the Windows service → use a UNC path if the folder is on a shared or network drive.

2. Open the Winbooks.ini file

   • Check for the presence of the UsersPath variable.

   • If the variable is missing or empty → This is most likely the issue (often happens when the connector is installed on a proxy server instead of the main server).

3. Verify the folder specified in UsersPath

   • Make sure the folder exists.

   • Check that it contains the Users.dbf file.

   • ⚠ Same rule: if the folder is shared or on a network drive, replace with a UNC path in the winbooks.ini file

4. Check the Users.dbf file

   • This file contains the list of all companies (1 row = 1 company).

   • Each company entry specifies the path to its DB/DATA folder. If your path is leading to a network drive, this path has to be a UNC path.

   • ⚠ The file is encrypted → the connector automatically decrypts it and creates a temporary decrypted file in:

     C:\\Program Files (x86)\\WinbooksService\\tmp . This file will only be visible when a request is performed to the service.

There is an example of a users.dbf file once opened, you have the CODESOC column referencing the folders codes and the path indicating the related paths.

• To verify:

  • The company code entered in Chift matches a company in the file.

    • If no match is found in the file, then the connector won't work. You can re submit the form on Chift to change it without having to reinstall the service

  • The path specified for the DB/DATA folder is valid and accessible.

    • If the path does not exist or is not accessible by the user running the service, then it cannot work. You thus have to update the user running the service as explained in the detailed troubleshooting section.

  • The path exist, is correct but is not UNC and is associated to a network drive, then you have to update this file to have the UNC path and not the local path. This won't change anything to your winbooks configuration as those 2 paths are the same for your machine but will allow the service to know where to look for winbooks related files