x Want to participate? Join the group to interact
New

Support for load bearing/roaming servers

I recently had a case where 1 user was affected when trying to generate payments, several times when they logged in to process the payments it wouldn't generate a unique number, as it is meant to do and this would cause issue with the process.

The business are using a multi server load balancing protocol, which is when any user logs in the server will divert the user to the server with the least amount of traffic. This has been narrowed down to what is causing the issue, however there doesn't appear to be a fix for this.

So the idea is to have Sage support for load balancing server to alleviate the issues encountered when generating payments or processing any other function within Sage 200

Adam Butler

  • Hi Adam. Are you referring to the payment number that is part of the EBanking module? With the HSBC EBanking module, the sequential numbering is stored in the Common data folder on the client PC. With a single RDS server, this would be common to all the users on that RDS server but wouldn't be visible to another RDS server or other workstations. If this is the problem, the resolution is to fix the issue in the EBanking module so that the common data can be relocated to a network share. 

*Community Hub is the new name for Sage City