Sage 100

 View Only
  • 1.  Customer in 2017 Advanced. Have followed KB artic

    Posted 03-05-2018 09:23
      |   view attached
    Customer in 2017 Advanced. Have followed KB article alternatives....ports...firewall...no luck. Any ideas???


  • 2.  RE: Customer in 2017 Advanced. Have followed KB artic

    Posted 03-05-2018 09:33
      |   view attached
    Not sure if you've seen this article or if it's related.

    Attachment(s)

    pdf
    Windx_Error.pdf   37 KB 1 version


  • 3.  RE: Customer in 2017 Advanced. Have followed KB artic

    Posted 03-05-2018 09:34
    Try pinging the server name, replace server name with IP address in the shortcut -- I know these probably duplicate what is in te KB but this is what seems to work most times for me.


  • 4.  RE: Customer in 2017 Advanced. Have followed KB artic

    Posted 03-05-2018 09:52
    Not sure if you are on a terminal server (Let me know if you are, and how many users are connecting, as there is a registry change required to fix this issue. ). Also, in addition to what is in the PDF article, make sure that the high ports on the Firewall on the Sage application server are open inbound, namely, ports 30000-65535/TCP


  • 5.  RE: Customer in 2017 Advanced. Have followed KB artic

    Posted 03-05-2018 19:32
    So the Launcher starts but you can't open any task right? Try this: For 1 user, check the Spawn Task from Application Server in User Maintenance / Preferences. **Note:** In case you tried this option already make sure you close Sage completely (close the Launcher) and restart. If you don't exit the change will NOT take effect.