Sage 100

 View Only
  • 1.  windx error cannot find server - sage adv 2018 to 2022 - same server

    Posted 08-09-2023 10:50

    Client is upgrading from sage 100 adv 2018 to sage 100 adv 2022. installed on same server as 2018. 2018 sage service is on port 10000, 2022 is on port 9922. sage runs from the server but not from a test workstation. 2018 runs fine from the same test workstation.

    I tried changing the shortcut and SOTA.ini to the ip address - no luck

    I cleared locate and sessions - no luck

    Disabled windows firewall on both the server and workstation - no luck

    Not sure where to go from here.

    Thanks in advance for your help.



    ------------------------------
    Greg Stiles
    S & W Microsystems
    ------------------------------


  • 2.  RE: windx error cannot find server - sage adv 2018 to 2022 - same server

    Posted 08-09-2023 10:59

    Cannot find server is different than finding the server but nothing is running on that port.  What is the exact error?



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



  • 3.  RE: windx error cannot find server - sage adv 2018 to 2022 - same server

    Posted 08-09-2023 11:22

    Yes @Kevin Moyes you are right.  The error is "Unable to connect to server: "NTMASAGE" The server cannot be found"



    ------------------------------
    Greg Stiles
    S & W Microsystems
    ------------------------------



  • 4.  RE: windx error cannot find server - sage adv 2018 to 2022 - same server

    Posted 08-09-2023 11:33

    That's a network problem / name resolution. 

    Maybe re-run workstation setup and use the IP address from the beginning?



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



  • 5.  RE: windx error cannot find server - sage adv 2018 to 2022 - same server

    Posted 08-09-2023 12:25

    Not sure exactly what I did that fixed it but I was able to get it working. I did have a typo in the firewall rule for pvxwin32 and uninstalled and recreated the service a few times trying different ports. I'm good now. Thanks for the help @Kevin Moyes, you focused my thoughts.



    ------------------------------
    Greg Stiles
    S & W Microsystems
    ------------------------------