Sage 100

I have a client running Sage 100 Advanced vs 2014, pu 4. We are testing the deployment of a new module. They have a test server dedicated to Sage 100 and another test server dedicated as a Terminal Server. Both are virtual servers running Windows 2012 R2. Because we are in a test environment, we have fewer than 10 people in at any time. Periodically, a user will have their Sage 100 session drop. When this occurs, the users session has typically been idol for a few minutes or more. When they return to doing data entry in a particular Sage 100 entry screen, an error will flash and then the entry screen will close. The error flashes too quickly for the customer to get a screen shot but she says it references ""lost connection"" or something similar. When she tries to reopen the date entry menu option in Sage 100, the program just closes. She can then relaunch Sage 100 and continue working until the next time the problem occurs. We can't find any rhyme or reason to when it happens. Sometime the drop occurs in 30 minutes. Other times it can go 6 hours between drops. There's nothing written in the Sage 100 activity log other than the user logon's. I can't find any orphaned pvxwin sessions running on the terminal server or the Sage 100 server. Their IT guy says he has removed all anti-virus tools from both servers and that he has confirmed the TS licensing server is running and updated. Anyone have any bright ideas?

Just a shot but have you tried setting users to Spawn tasks from server?

Are they running the server as an app or a service? I would try to do the registry edit. In the 90minds Evernote or Sage KB search for ""Cannot Create a New Session with a large number of users"" and follow steps for the registry edit there.

Also - performing the following couldn't hurt either: Have all users exit Sage MAS 200. Stop the Application Server and close Application Server Configuration. On the Sage MAS 200 server, rename ..\MAS_System\SY_Console.m4t file On the Sage MAS 200 server, rename ..\MAS_System \SY_Workstation.m4t file On the Sage MAS 200 server, rename ..\home\lib\_appserv\LOCATE.PVK On the Sage MAS 200 server, rename ..\home\lib\_appserv\SESSIONS.PVK Delete the contents of the MAS90\Locks folder Restart the Application Server. Open Application Server Configuration. A new LOCATE.PVK and SESSION.PVK files will be automatically recreated. On the Application Server Configuration, go to Server Tab, set KeepAlives = Off On the Application Server Configuration, go to Clients Tab, set Reconnect = None

Sometimes the Kerberos settings can cause issues where users are dropped. Extending the life of the Kerberos ticket has resolved some of these for me.

Is Automatic Logoff enabled in User Maintenance? I had similar symptoms on 2013 Advanced, which Sage attributed to a bug.

Our support team worked on this very same issue last month for a client. Running as an App helped for a few weeks, then it came up again. Let me touch base and get our Sage Case (and Tech) info. And if we resolved the issue, I will pass that along too. In my client issue, they could click on the Sage Icon and go back to work. no user ID or password prompt.

ok, Running as a Service with the recommended Registry Changes; Spawn Tasks for EACH user (all users) turned On, and Switched Data Execution Prevention to be for only essential windows programs. That seemed to resolve the issue at our client.