Error: "Windx Client Connection: The application server is reachable but is not accepting requests on TCP socket given" or "Unable to connect to server." or "The server is reachable but is not accepting request on TCP/IP socket given..."

Summary

Error: “Windx Client Connection: The application server Is reachable but is not accepting requests on TCP socket given” when starting Sage 100 Advanced or Premium

Error: “Unable to connect to server. The server is reachable but is not accepting request on TCP/IP socket given. Most likely the application server is not running on the server.” when starting Sage 100 Advanced or Premium

Resolution

Possible Resolution (if all workstations receive same error):

One or more system files for the Application Server Configuration module are damaged. Application Server Configuration controls the startup path for the service, port number, and other items for Sage 100 Advanced or Premium. This error can also cause runaway pvxwin32 tasks on the server when starting the application.

Resolution 1- Check if the Sage 100 Application or Service is running.

If Sage 100 is set to run as an Application, then log onto the server, open the Application Server Configuration, and check if it is already running. If not, Start it.
If Sage 100 is set to run as a Service, then log onto the server, open Control Panel, Administrative Tools, Service, and check if the Sage 100 service is already running. If not, Start it. (You might also want to right-click the service to look at Properties, Recovery tab. There, make sure to set “Restart the Service” upon First and Second Failures.)

Note: Do not run both Sage 100 as both an Application and a Service at the same time!

Resolution 2: Replace the LOCATE.PVK and SESSIONS.PVK files.

Have all users exit Sage 100 Advanced.

Stop the Sage 100 Advanced Service or Application (and close Application Server Configuration)
On the Sage 100 Advanced server, rename the “..\MAS90\Home\Lib\_Appserv\LOCATE.PVK” file.
On the Sage 100 Advanced server, rename “..\MAS90\Home\Lib\_Appserv\SESSIONS.PVK” file.
Open Application Server Configuration and Start the Application Server.
Have someone log into Sage 100
New “LOCATE.PVK” and “SESSIONS.PVK” files are automatically recreated and the original grid restored.

Note: If Sage 100 Advanced is normally run as a Service, then: log users out, stop the Application, start the Service, allow users in.

Resolution 3:

Change the “..\MAS90\Home\Launcher\SOTA.INI” file (on the workstations) to include IP Address instead of Server Name. This resolves the issue for workstations on the network that are not able to complete server name resolution.

Resolution 4:

Restore the “..\MAS90\Home\Lib\_Appserv” folder from a backup.

Resolution 5: Restore the following Sage 100 Advanced system folders from a recent good working backup (after renaming the current folders):

“..\MAS90\Home“
“..\MAS90\Launcher“
“..\MAS90\SOA“
“..\MAS90\MAS_System“

Note: If restoring “MAS_System” from backup and using Paperless Office, make sure to put back in the “PL*.m4t” data files from the current “MAS_System” folder that was renamed

Possible Resolution (if only one or a few workstations receive the error):

There may be a Windows or network security or permissions issues, such as a port is blocked or is actively in use by another program. Contact your network administrator or a qualified technician.

Note: It is also possible under this scenario for all workstations to receive the error, while there is no problem in accessing Sage 100 Advanced from the server.