Sage 100

Have clients moving from Sage 100 Standard to 100c advanced. On multiple occasions they are running into issues running as a service but everything is fine when running as a logged in application. I'm requesting more details on whats not working, but has anyone else seen this?

There seems to be a magic number of tasks per server, and once you hit that magic number, you're better off running as a desktop application. I always heard that it was ~75 tasks, but I recently had a client with newer hardware have issues at like 40 tasks. Plus we seem to always have to check the Spawn Tasks if Sage is virtualized.

Years ago I remember it having to do with some kind of files handles issue with windows and services. I thought there might have been a registry tweak.

I have a Sage 100 2017.1 Perpetual where I have been researching an issue where user Sage 100 task windows close but NO error condition. They are not at the level where I think number of tasks impacts them and that also traditionally throws off error messages. In my end user's case they get no error. They will just be looking at a screen such as customer maintenance and suddenly that screen closes. This was also ongoing with Sage 100 2014 - both Advanced running as a service

Did the problem go away if you switched to application?

Yes

We saw something similar at another client. Make sure all powersave and sleep functions are turned off on the workstation.

Sorry, should have said that running as standalone resolved the issue. Have not yet tried running the server as an an application vs service. Lots of IT push back/conflict. I'm nearly positive this is something local but about to push it to Sage and prepare for the flame thrower.

re: power saver, holy water sprinkling, anti-virus - been trying since v2014.

What do you mean by 'running as standalone'?

I believe it has to do with Windows memory allocation to a service being more restricted (by default) as compared to an application. There should be a KB article with registry tweaks as an alternative to running in Application mode.

I think this is what Kevin is referring to -- https://goo.gl/r2ILQh

Task Widows Random Closing KB - https://goo.gl/C41Ubd

How to run Sage 100 Advanced in standalone (aka MAS90) mode - https://goo.gl/9kdQJD

Thanks all. Let me try this

Either you need to apply the registry edit for the services ""memory heap size allocation"" noted in KB article on (I know because I wrote the original article :-) OR the fact the service is running under the LocalSystem account (bad) instead of a domain account (good). If they report issue as ""X number of users are able to get in ok but then get timeout error / hanging opening a new screen"" then do the registry edit and don't forget to reboot server for it take effect.