Weighsoft integrates with Sage 200 by directly reading the Sage 200 database. If you have created a new account in Sage 200, taken an account off stop, or put an account on stop, but the change has not come through to Weighsoft, the issue is likely related to the Isys Credit Control service running on your server.
đNote: The steps below assume the Isys Credit Control service is running. If the service is not running, this will need to be started before investigating further.
Possible causes
If the Isys Credit Control service is running but accounts are still not syncing, there are three likely causes:
The user account the service is running under does not have access to the Sage 200 database location.
The user account the service is running under does not have permission to access the Sage 200 database location.
The database server Weighsoft is pointed to for Sage 200 is not the live version â the system is reading data, but changes made in Sage 200 are not being picked up.
Resolving the issue
No access or insufficient permissions
If the service does not have access to, or permission to read, the Sage 200 database location, this will need to be resolved by the person who manages your Sage 200 installation and server. They will need to ensure the service is configured to run under a user account with the correct access and permissions.
Wrong database server location
If Weighsoft is pointed at the wrong database server â for example, a test or backup version rather than the live database â please contact Support with the correct database server location so we can update the configuration in Weighsoft.