Sage 100

v2016 Std running on I-BN cloud. Things were great until yesterday when the Sage Exchange update popped on them. Client said they said ""no thanks"" and went about their business. Today all heck breaks lose on their system. When they click on a panel (vendor maintenance ALE button), one of the error 12 message appear. They can click by it and continue working. However, whenever they click on a report to generate, they get the Sage 100 has stopped working message. I-BN has 1. Reinstalled new Citrix Receiver on Jill's PC 2. Deleted user profile from the server 3. Test using different user credential and received the same error message 4. Removed CSPXA76SAG07\C$\Users\jedwards\Documents\SAGE 100 folder and noted that SAGE 100 folder incates that she is using Standard Desktop. 5. Updated her Desktop settings as ""Classic"". Anyone run into this before? Sage 100 runs fine for me but I am accessing it from their I-BN Sage server which is a different install than their Citrix workstation connection.

Have you tried uninstalling all versions of Sage Exchange on the Citrix client and then re-installing Sage Exchange? Maybe something got corrupted in the registry during the upgrade/installation.

Issue is resolved. User was using the lovely ""Standard Desktop"" versus the Classic Desktop and we believe this caused the issue with (1) the SAGE 100 has stopped working error she was receiving and (2) the issues with the custom SAGE windows. All is well today.

It happens when the 2nd user thru the TS or Citrix server goes into using the Standard Desktop right? There was a Sage fix for 2016 for this. I had posted about this issue back then. I'll see if I can find it. We got a pre-release version of the Launcher fix which was then going to be included in the pending product update.

Linda Cade has said that fix wasn't going to be available until a new master was created, i.e., v 2018 since it required a language interrupter update. Unless this something else?

Oh. Good to know.

So ultimately, if client switched to 100c to get the new desktop AND they are running via RDP, they can't use the new standard look? I want my money back!!!!!

Possibly a browser issue? Use Chrome instead of IE as the default?