Sage 100 Unable to Connect to Server

Description

Sage 100  “Unable To Connect To Server ‘[Servername]’. The server cannot be found.”

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 operational 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.

• Incorrect Server Name, IP Address, or Port
• Network DNS issues
• Firewall Security
• “Session.pvk” is corrupted (does not apply to Sage 100 ERP Standard edition)

Resolution 

Verify that the correct IP address or server name was entered during workstation setup.

1. Browse to the “..\MAS90\Launcher” folder on the workstation.
2. Open the Sota.ini file.
3. Locate the [Servers] section. The IP address or server name is listed after the following text: “1=”
   Example: 1=ServerName;10000;APS=SAGE;APPLICATION=Sage 100 ERP;Path=\\ServerName\ShareName\MAS90
4. If the IP address or server name is incorrect, Enter the correct Server Name or IP address or uninstall and then reinstall Workstation Setup.
5. Verify the port is open (not blocked by a firewall).
6. Verify the IP address or server name and port were entered correctly in the icon properties
   1. Right Click Sage 100 ERP workstation client icon and select properties
   2. In the Target confirm the server name or IP address and port are correct
      Example: “..\MAS90\Home\pvxwin32.exe ../launcher/sota.ini *Client -ARG “ServerName or IP address” “Port” “Sage 100 ERP”
      (“..\MAS90\Home\pvxwin32.exe ../launcher/sota.ini *Client -ARG “MyServer” “10000” “Sage 100 ERP”)
      (“..\MAS90\Home\pvxwin32.exe ../launcher/sota.ini *Client -ARG “192.168.1.1” “10000” “Sage 100 ERP”)

If Port, ServerName, or IP Address have been verified correctly in the above steps, this message can occur if an Inbound Rule and Outbound Rule has not been created for the Sage 100 (formerly Sage 100 ERP) port on the Windows 2008 or 2012 Server, under Windows Firewall Advanced Security.

1. Open Administrative Tools, Windows Firewall with Advanced Security console
2. In the left pane of the console, select Inbound Rules
3. Right-click select New Rule
4. Select Port click Next
5. Select Specific Local ports and enter the port number for Sage 100 and click Next.
   • Note: The default port is 10000. However, port numbers are often selected during installation of Sage 100
6. Select Allow Connection click Next
7. Select Domain, Private, Public and click Next
8. Name the new rule a name of your choice.  Add a description identifying the rule is used for Sage 100 and click Finish
9. Create an OutBound Rule following steps above.

Replace the “Locate.pvk” and “Sessions.pvk” files (for Sage 100 Advanced or Premium editions only):

1. Have all users exit Sage 100 ERP Advanced or Premium
2. Stop the Application or Service running Sage 100 ERP
3. On the Sage 100 Advanced server, rename the “Locate.pvk” and “Sessions.pvk” files found within “..\MAS90\Home\ Lib\_Appserv“, the folder where Sage 100 ERP is installed.
4. Open Application Server Configuration from the Windows Start Menu
5. New  “Locate.pvk” and “Sessions.pvk” files are automatically recreated and the original grid restored
6. If Sage 100 ERP is run as:
   • an Application, log back into Sage 100 ERP
   • Stop the Application, Start the Service, and log back into Sage 100 ERP 

Support

If necessary, seek the assistance of Acute Data Systems to help provide assistance with this process.