Sage 100

 View Only

  • 1.  Sage 100 v2016 on Windows 2016

    Posted 12-03-2020 11:30
    We've encountered an oddity during a cloud migration of Sage 100cloud v2016 Advanced to a Windows 2016 server.

    It seems that if we select "Classic" desktop everything is fine. But if we select "Standard" then the Sage client appears to load but never displays. The only possible cause we can hypothesize is that the server has reduced color range, it not at 16-bit? 

    Has anybody experienced this? Solved it?

    Also, where can we reset the user's Sage Desktop selection so they can choose again?

    ------------------------------
    Jerry Norman
    VP, 90 Minds
    Smartbridge Partners
    512.419.1444 x112
    ------------------------------


  • 2.  RE: Sage 100 v2016 on Windows 2016

    Posted 12-03-2020 11:35
    The reset is easy.  Just delete the Sage 100 folder out of the user's My Documents folder.  This also removes their "Favorites" but if it's a new server that shouldn't be an issue.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 3.  RE: Sage 100 v2016 on Windows 2016

    Posted 12-04-2020 16:15
    @Kevin Moyes, I discovered that you don't actually have to delete the whole directory.  All you have to do is edit the "bootstrap.json" file.  There is only one line in the file and this is that line:

    {"OldLauncher":"launcher.old.exe","NewLauncher":"launcher.2016.exe","Selection":0,"BrowserEmulation":8000,"Locked":false}

    The "Selection":# is the key.  The "0" will select the "OldLauncher" and if it's "1" then the "NewLauncher" will be selected. 

     ​

    ------------------------------
    Chuck Peddy
    Smartbridge Partners
    ------------------------------

    Original Message


  • 4.  RE: Sage 100 v2016 on Windows 2016

    Posted 12-04-2020 16:28
    Good to know @Chuck Peddy
    We normally saw this most with upgrades, where retaining the other settings wasn't important, and didn't dig into the fine details.
    ​

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 5.  RE: Sage 100 v2016 on Windows 2016

    Posted 12-04-2020 00:55
    Edited by George Khairallah 12-04-2020 01:29

    I believe this is a bug in 2016, I don't recall if this applied to Standard vs the Classic interface, but the solution for 2016 specifically is that all users must be using the same interface. In the cases we've experienced, we always recommended all users use the classic interface and the issue went away. 

    Of course, this was the case in a Terminal Server environment, I’m not sure if there are server side variables that could cause the same behavior in a non TS a environment. 

    What I don't recall is if it'll equally work if all users use the Standard interface... 


    ------------------------------
    George Khairallah
    CTO | gotomyerp, LLC
    george.k@gotomyerp.com | 877-888-5525
    http://gotomyerp.com/
    ------------------------------



Related Content