Sage 100

We had a larger client that started having numerous Sage 100 errors on the server. Sage 100 had been stable in the environment for quite some time and nothing appeared to have been changed. The errors appeared to be connectivity oriented at first glance. On further review, I found that the processor was almost 100% and Sage 100 was timing out. The MAS Server was on Hyper-V and it appears the Server Profile had been changed to only allow 1 Core. We changed the config to allocate 4 cores and all is back to normal. I thought I would share to remind everyone that resources can be changed in a virtual environment which something that can be easily checked if there are significant performance issues or other errors.

Could you share the instructions on how to check this for those of us who are not a trained network technician?

Had similar situation where customer virtualized and suddenly everything ran very very slow on Sage 100. Would love to see some step-by-step instructions on how to check or have the IT folks check.

Here is a screen shot of the Hyper-V Manager. The VM has to be off to change anything.

@PhilMcIntosh You beat me to it. VMWare is similar. The group should get the IT guys to screen print this on a troubled site. It can posted here if they are not familiar with Hyper-V or VMWare. There are also some load balancing tools that IT can use that will show resource limits reached. I have seen those more on the VMWare side but typically my IT techs are looking at that for me. Load balancing is importing in our banking practice where as we can have 30-40 Virtual Server on our VMWare hosts. Obviously it is even more of a factor in cloud deployments.