Sage 100

 View Only
  • 1.  Just upgraded a client to 2014.3 Advanced single w

    Posted 01-08-2015 12:39
    Just upgraded a client to 2014.3 Advanced single workstation and the workstation will only connect if the application server is running as an Application, not a service. If I run it as a service, they get the ""server cannot be found"" message. I've gone through all the KB articles I could find and created the inbound/outbound rules and verified sota.ini. The only weirdness in the install was it told me the integration engine couldn't be installed. Is that what is causing this? @Sage100UrgentSupportNeeded


  • 2.  RE: Just upgraded a client to 2014.3 Advanced single w

    Posted 01-08-2015 12:44
    Have you tried selecting the ""Spawn tasks from server"" in User Maintenance?


  • 3.  RE: Just upgraded a client to 2014.3 Advanced single w

    Posted 01-08-2015 12:48
    Thanks for your response! I apparently had a user account with not enough rights set up to log the service on. Once I switched that back to just ""local account"" the workstation connected. Now I just have to find the correct user :/


  • 4.  RE: Just upgraded a client to 2014.3 Advanced single w

    Posted 01-08-2015 12:50
    Remember that local account can't see other servers --- so if for example you try to use paperless and it is on another server you may run into an error. Check this link out - I stole it from an excellent amount of info @AlnoorCassim provided a few years back http://www.s-consult.com/2008/10/08/tips-how-to-set-up-an-application-server-in-sage-mas-200-version-4x/


  • 5.  RE: Just upgraded a client to 2014.3 Advanced single w

    Posted 01-08-2015 13:45
    Ah yes, the Alnoor ""bible"" I give a copy of that to every advance installation I encounter and insist they follow it. PRICELESS!!!


  • 6.  RE: Just upgraded a client to 2014.3 Advanced single w

    Posted 01-08-2015 17:38
    Has this same issues at a new client today. I searched the web, and that article @WayneSchulz mentioned above, floated to the top and fixed my problem. I guess i owe @AlnoorCassim the thanks!