Sage 100

We have a client running MAS 200 4.40.0.10 with JobOps on 64 bit Windows Server 2008 R2 Enterprise SP1 server with Xeon CPU-2640 @ 2.5GHz with 10 GB RAM. The users log in via RDP. The terminal server is a separate box. MAS is running as a service and we occasionally get problems where a user session ""locks up"" by throwing an error on the MAS server. The error has to be cleared before the user can log back into MAS. This happens about twice a week and it can be a hassle to clear the error. Does anyone have any ideas as to what might be triggering these errors?

How many total users? Have you used the registry hack for expanding memory available?

Up to 35 users. I don't think I've applied the registry hack. Could that help?

I think the hack is the next logical option. Unless you want to run it as an application for a week to see if the issue is resolved. If it is, then the hack is the next step.

The application route doesn't work so well either. We have run it as an application and that produces the error as well. Can one of you provide me a link to the hack? I know I've looked at it before but I don't know if I've saved the link.

I think this is the KB entry http://support.sagesoftwareonline.com/mas/query/index.cfm?action=abcdetail&abc_id=210