These values are based on the environmental testing of a single tier environment utilizing Windows Server 2019, Windows SQL Server 2019, and Sage X3 Runtime R94.1.X versions. All values above are estimates and solely used to better understand the sizing of the registry value as it pertains to the session usability. All environments are unique (treated as such), and adjustments of these values will need to be vetted in a test environment.
There has been noted improvements to the environments by also adjusting the maxmem and sadmem folder values for the impacted folder endpoints (in addition to above recommendations). These values can be found by navigating to Setup, General parameters, Folders (GESADS), selecting the impacted folder from left list, then loading the Miscellaneous tab
CAUTION: This solution needs advanced Operating System knowledge. Consult your system administrator for help. Sage isn't liable for issues caused by improper changes to the Windows Registry. Always back up your data before applying advanced solutions.
CAUTION: Sage support can't assist with third-party products, hardware, report customizations, or state and federal tax questions. Refer to our Scope of Support for more info. Contact your Sage business partner, network administrator, or accountant for assistance.Microsoft Windows Heap Memory allocation (SharedSection) configuration guidelines for Sage X3 Environments.
The chart below shows estimated values for configuring the non-interactive desktop Heap Memory allocation (SharedSection) as it pertains to Sage X3 active Convergence Sessions (AKA Classic Sessions) generated by the Runtime Server component. These changes are made to the Microsoft Windows Registry. See further down the article on how to change these Windows Registry values.
| 3rd registry parameter | Max # of runtime sessions |
| 768 (default) | 136 |
| 1024 | 182 |
| 2048 | 364 |
| 4096 | 729 |
| 8192 | 1457 |
| 10240 | 1820 |
| 16384 | 2913 |
| 20480 | 3640 |
Changing the Registry Value:
Before you begin:
WARNING: This is a Windows registry change. The proper precautions should be followed (i.e. backup or restore points) before attempting to change Windows Registry configurations.
DocLink: Batch Server Tasks increasingly failing with ECONNRESET errors
DocLink: ERROR: ECONNRESET errors
DocLink: Batch Server Tasks fail with ECONNRESET errors