Sage 100

What is the purpose of this file - Launcher.old.exe Under the Launcher folder??? Client is experiencing ""bootstrap errors"" upon startup (2016 Std) and IT has fessed up to deleting this file about 20 minutes before the Shxx started hitting the fan. Sage100ERP Launcher bootstrap error. Nothing on Sage KB. Is this a red herring or the issue?

I deleted it once and had to immediately put it back. I don't know what the deal is, but it appears to be required. I had forgotten all about that!

I hit this before also. I am looking up my notes on what exactly it does but, YES, restore the file!

From what I can tell, this file is a kind of ""bridge"" between the old Sage 100 (MAS 90) and the new Sage 100c protocols. I'm not certain about that but I have only encountered it when running 2016 and I have experimented jumping between regular 100 and 100c on the same install and the nature of the file seems to change.

@ChuckPeddy - Where were you in Chicago? I was wanting to show you my old stomping grounds. Thanks all for the posts. Waiting to hear back from client. It was one of those ""I was in the folder and I noticed the file containing the word old so I deleted it......

@JeffSchwenk , I couldn't make it to Summit for the first time in 12 years. It kinda bummed me out. I did follow the Social Media updates and wonder if Sage is really committed to coming back around. From what I can tell with the research I did on the launcer.old.exe some time ago, the system used to have Launche32.exe as the only executable in the Launcher folder. That changed with 2016. It is merely speculation on my part (I couldn't get a straight answer from Tech Support) that the new configuration uses the two new files (Launcer.2016.exe and Launcer.old.exe) to differentiate between the new and classic Sage 100 desktop. I ran into this issue in an upgrade where the IT people had squirrely rights setup and the the average user could not access the Launcer.old.exe file. They received an odd error when launching Sage 100. Once proper rights were granted things fixed themselves.

@ChuckPeddy-missed you at Summit!

@ChuckPeddy I missed you too!

Thanks, @JaneCavanaugh and @KellySappington , I really missed seeing everyone!

Just had this issue upon upgrading to v2017.2 on new server. However, at first I was looking at the Launcher folder in the main v2017 folder on the server, and the file was present. I eventually realized I needed to be looking at the local c:\sage\ workstation folder on the server, which in fact was missing the file - deleted by Symantec.