Sage 100: We just updated to MAS200 V4.50SQL and much to my dismay, we still can not run it as a service. We started it as a service, but once we had about 10 users on, running a few programs each, it locked up and we were forced to run it as an application. Why can this not be fixed?

Votes

7 We just updated to MAS200 V4.50SQL and much to my dismay, we still can not run it as a service. We started it as a service, but once we had about 10 users on, running a few programs each, it locked up and we were forced to run it as an application. Why can this not be fixed?

by: Marvin G. | over a year ago | General Enhancements

Any reboot of the server, requires re-starting the application. For a program like this, it needs to be able to run as a service to make it more reliable

by: Marvin G. | over a year ago | General Enhancements

There have been workarounds for this in the past (I believe involving registry changes). You might look in the Sage KB.

This really needs to just be fixed within the product so it works as advertised.

by: John B. | over a year ago

7

We just updated to MAS200 V4.50SQL and much to my dismay, we still can not run it as a service. We started it as a service, but once we had about 10 users on, running a few programs each, it locked up and we were forced to run it as an application. Why can this not be fixed?

Comments