Further analysis and investigation of this issue appears to show that this only occurs when running Sage 200 in a virtual environment, typically a Hyper-V virtual machine. We are yet to receive any reports of this issue in a non-virtual environment.

When accessing System Administration, various messages appear throughout the initialisation, including those referring to the core components and the building of models. The program may hang or freeze at any of these stages.

Check available resource on the virtual machine

You must ensure that the virtual environment meets the minimum requirements set out in the System Requirements Guide for Sage 200. For standard single-server environments, this requires at least a dual-core processor and 4GB of RAM. Almost all environments that have encountered the above issue have not met the minimum requirements set out in the guide. As a result, during the installing of the core components, the full resource of the virtual machine is used up and System Administration cannot properly install the components.

If necessary, shut down the virtual machine, change the number of processors from 1 to 2 and set the available memory to 4096MB (or higher if possible). If you require assistance with this, please refer to the help available with the virtual environment software such as Hyper-V.

We recommend you do not use dynamically allocated memory whilst we are investigating this issue.

Check user groups and user names

When setting up the Sage 200 Services and Sage 200 Secured Services users, please ensure that they are assigned to the relevant groups only. We have found that adding the user names to the wrong groups can also prevent the core components from installing successfully. Use the table below to check the user names are assigned to the correct groups.