Sage 100

 View Only

  • 1.  "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-06-2022 18:26
    Client purchased Job Cost so I installed it today.  After the installation, I started the app back up (not running as a service) and I am getting this from any workstation.  I rebooted, because the app is set to start automatically when you login, and am still getting it, so I'm sure it's the same app as before and the same workstation shortcut as before.
    The server is the right server, the port is the right port (have checked the shortcut and the sota.ini on both).  WTH?????????????

    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------


  • 2.  RE: "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-06-2022 18:33

    If it runs from the server, but not the workstation, then maybe something happened with the firewall that's now blocking the connection. Just a guess, but I would start there.






  • 3.  RE: "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-06-2022 18:38
    Not running from the server, either.  It's just staring me in the face, where I can SEE the app running, and telling me it's not running.

    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------

    Original Message


  • 4.  RE: "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-06-2022 18:45
    Something else probably grabbed the port. From a command-line run:

    netstat -aon | find ":10000"

    (where 10000 is the port you expect Sage to listen on)

    The far-right number is the PID (process ID) of the program that snagged the port number, which you can then find in Task Manager. Hopefully you can tell what it is and are able to restart it.

    ------------------------------
    Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
    ------------------------------

    Original Message


  • 5.  RE: "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-06-2022 18:47
    Got it - I renamed the locate and sessions files and restarted it and now it's OK.  THANKS EVERYONE, false alarm.
    Can be moved to regular Sage 100.

    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------

    Original Message


  • 6.  RE: "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-07-2022 12:26
    Edited by Alnoor Cassim 11-07-2022 12:27
    @Steve Iwanowski - Nice! I didn't know with netstat that one could pipe through "find" on the port and get the PID that way. Thx for sharing that!

    ------------------------------
    Alnoor Cassim
    ------------------------------

    Original Message


  • 7.  RE: "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-06-2022 18:46
    Try starting up Mas90 style. If it doesn't work, at least you should see a better error message. If it does work, I wonder if 1 of the app server data files needs to be replaced. This can be done by:
    1. Stopping the App Server. Verify there are no linger pvxwin32.exe's with the Task Manager.
    2. Renaming sessions.pvk file in \mas90\home\Lib\_Appserv
    3. Running App Server Config. This will create a new sessions.pvk
    4. Start up the normal way directly at the server
    5a. If that works from server, start up the normal way from the workstation.
    5b. If doesn't work from wkstn, I'd suspect the Windows Firewall may enabled on Sage Server and you need to go into it to add inbound rule for the App Server port.

    ------------------------------
    Alnoor Cassim
    ------------------------------

    Original Message


  • 8.  RE: "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-06-2022 18:50
    Dang, thanks to everyone who was bored tonight!  And BTW - I DID make a backup first, @Bill Pfahnl, which is probably why this happened... HA​

    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------

    Original Message


  • 9.  RE: "Unable to Connect to Server. The server xxx is reachable, but it is not accepting requests on the TCP/IP Socket given. Most likely the Application Server Service is not running on the server"

    Posted 11-06-2022 18:47
    If you copied the MAS90 folder before installing J/C then maybe you could swap it out to see if it's the installation vs the environment.

    ------------------------------
    Bill Pfahnl
    Nims & Associates
    ------------------------------

    Original Message


Related Content