Windx Client Connection “error: Unable to connect to Server: ‘[Servername]’. The server cannot be found.”

Description

• Sage 100 Advanced workstation – new installation when launching for the first time shows a gray screen that and says (not responding), then shows error message with Windx Client Connection “error: Unable to connect to Server: ‘[Servername]’. The server cannot be found.”
• This Windx Client Connection error “error: Unable to connect to Server: ‘[Servername]’. The server cannot be found.” can also display on an existing Sage 100 ERP Workstation install that has been working.
• How to create Inbound Rules on Server

Disclaimer

Network Warning
This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions.

Cause

• Permissions on the Application Server’s firewall is not allowing communication through from the workstation
• Server name cannot be resolved via DNS

Resolution

Create Inbound rule for PVXWIN32.exe process on the server in Windows Firewall

1. Open Control Panel, Administrative Tools, Windows firewall, Advanced settings
2. Right-click Inbound Rules and select New Rule
3. Select Program, click Next
4. Select “This program path:” and browse to <<drive letter>>\..\mas90\home\pvxwin32.exe (i.e. C:\Sage\MAS90\Home\pvxwin32.exe) on server
5. Select Next until get to ‘Specify the name and Description of this Rule’ screen
6. Enter Name for Rule
7. Select Finish

Check if server can be reached using IP address rather than server name

1. Use IPCONFIG on server to determine the correct IP address
2. Right-click on the Sage 100 ERP shortcut, select Properties, and change the Server name specified in the Target command (follows -ARG command) to the IP Address for the server
   • For example, …*Client -ARG “Server1” “10000” becomes *Client -ARG “192.168.101.9” “10000”
3. Click on Apply
4. In the Sage 100 ERP properties, select Open File Location to go the Sage 100 ERP Workstation local folder
5. Browse to the \MAS90\Launcher folder in the local Sage 100 ERP Workstation folder
   • For example: C:\Sage\Sage 100 ERP Workstation\MAS90\Launcher
6. Edit the SOTA.INI file to replace the Sage 100 ERP server name for the server and path under the [Servers] and [Active Server] sections
   • For example: [Servers] 1=192.168.101.9;10000;APS=SAGE;APPLICATION=Sage 100 ERP;Path=\\192.168.101.9\Sage\Sage 100 Advanced ERP\MAS90\
   • [Active Server] 192.168.101.9;10000;\\192.168.101.9\Sage\Sage 100 Advanced ERP\MAS90\
7. Test the Sage 100 ERP workstation shortcut to confirm if it will now connect to Sage 100 ERP
8. If this connection is now working, they will need to confirm with their IT department as to why DNS cannot resolve server name

Have your IT support check network connections:
Even if your are able to ping the server most of the time, some networking issues can cause intermittent or incomplete connections to the server. Common causes are:

• Security software or operating system failures
• Networking hardware failures
• Bad network cables
• Failing network switches, routers or hubs
• Wireless network interference (wireless networks are not recommended or supported by Sage)