Sage 100

 View Only
  • 1.  Sage 100 2018 Advanced upgrade from 2013 server. O

    Posted 09-18-2018 11:57
      |   view attached
    Sage 100 2018 Advanced upgrade from 2013 server. One or two of the users are receiving this Sage.ERP100.Launcher.Bootstrap has stopped working on their Terminal Server session. Anyone have ideas or good guesses. I'd look in the Sage KB if it were accessible for more than 5 minutes


  • 2.  RE: Sage 100 2018 Advanced upgrade from 2013 server. O

    Posted 09-18-2018 11:59
    Cause Launcher.old.exe is missing from ...\MAS90\Launcher\ folder .NET Issues Resolution Restore ...\MAS90\Launcher\Launcher.old.exe from backup If issue is happening to a specific workstation, run repair on .NET Open Control Panel, Programs and Features Locate the Framework 4 entry Right click and select Repair Locate the Framework 4.5 entry and perform the same steps. Locate the Framework 4.5 SDK entry (if installed) and perform the same steps https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=79095&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=10907&cmd=displayKC&dialogID=458590&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true


  • 3.  RE: Sage 100 2018 Advanced upgrade from 2013 server. O

    Posted 09-18-2018 12:00
    Still not sure this is the resolution. Posted as x-ref


  • 4.  RE: Sage 100 2018 Advanced upgrade from 2013 server. O

    Posted 09-18-2018 12:01
    This is coming up after users log into Sage for the first time and are asked to select the desktop type.


  • 5.  RE: Sage 100 2018 Advanced upgrade from 2013 server. O

    Posted 09-18-2018 12:15
    Turned off DEP - no effect (though I need to reboot which is problematic when 20 people are in Sage)


  • 6.  RE: Sage 100 2018 Advanced upgrade from 2013 server. O

    Posted 09-18-2018 12:54
      |   view attached
    I found this. Not sure if it is the same but it looks similar.


  • 7.  RE: Sage 100 2018 Advanced upgrade from 2013 server. O

    Posted 09-18-2018 12:58
    Also, if the issue is only with the terminal server users you may try changing the properties of the Sage 100 program icon to Windows 7 compatibility.


  • 8.  RE: Sage 100 2018 Advanced upgrade from 2013 server. O

    Posted 09-18-2018 12:59
    They removed the user and recreated the account. We shall see if that solves the problems long term.