Sage 100

Sage 100 Advanced 2013.4 on Windows 2012 server (running as a service), Windows 8.1 workstations. It was just reported to me that starting a couple weeks ago, several, but not all users would have their Launcher disappear, although other tasks remained open When that happened, they could not save any work in the open tasks, and would have to shut all down and restart Sage. Last week, I renamed SY_Workstation & SY_Console, restarted server. Also had user log in in MAS90 mode to see if that made a difference. Problem still exists; and the user in question is running in MAS200 mode again. Today I witnessed that launcher was down, but other tasks were up, and she was able to save work (a PO) and create and save a new PO. Got Sage on the line, but (as so often happens these day), stumped the analyst. I want it to be AV or something system related. Of course, client claims nothing has changed in environment, and even it it had, why isn't everyone affected? Anyone had this occur (i.e. launcher dies, but other tasks stay active) and resolve?

this sounds VERY familiar but in a much older version. have you tried renaming the sessions.pvk in the MAS90\HOME\_APP folder? also look at the Sage activity log?

@DavidOverholt , nothing in the Activity Log. I tried renaming sessions.pvk and locate.pvk in _Appserv, but then the Sage 100 Application Server Service wouldn't start.

Sorry if this is stating the obvious but you did open Application Server Configuration after renaming the .pvk files, right? Just checking. Then if the service wouldn't start did you try running as app?

There's no errors in PC event log about Launcher crashing? Are there orphaned PIDs on the server after Launcher disappears?

@CullenLowe ummm, no, I didn't. @SteveIwanowski , don't know - there are about a dozen users on the system during troubleshooting. I'll follow up on your input and report back. Thanks!

Glad I mentioned it, then. If you haven't renamed those .pvk files yet you should do that now. I have seen those correct a lot of issues. Unlike SY_Console and SY_Workstation, when you rename Locate.pvk and Sessions.pvk they don't get automatically renamed when you log back into the system. You have to create them by manually starting the Application Server Configuration program. You don't have to leave it open or do anything else in it, but the act of starting it recreates those files.

Good to know!

They report that it happened to 2 users today (down from 5 users yesterday. IT reported that there were no errors in the event log about Launcher crashing. Maybe create new user ids?

That's bizarre only the Launcher would shut down. The opposite is more common where if there is a connection issue the Launcher would stay running because it is the only local task. It sounds trite but ask them to specifically exclude Launch32.exe from AV scanning and on the wkstn side, add Launch32.exe as a DEP exclusion (or even better set DEP to 'Essential Programs and Services' then reboot to take effect). In the old days there was a worm named Launch32.exe and once awhile it would crop up again as a threat on AV or anti-malware apps (especially SUPERAntiSpyware).

@AlnoorCassim they are not running AV on the server at all. I will pass along this info for the workstation side.