Sage 100 2019 unable to connect to server.
Sage 100 2019 unable to
connect to server
This error can occur due to the following
reasons: Incorrect IP Address, Server Name, or Port. Issue in the
Network DNS. Firewall Security.
Error: "Unable to connect to server:
<server name>. The server cannot be found" when starting Sage 100
Advanced or Premium
Causes of Sage 100 2019 unable to connect to server:
·
Incorrect Server
Name, IP Address, or Port
·
Firewall Security
·
"Session.pvk"
is corrupted (does not apply to Sage 100 ERP Standard edition)
·
Network DNS issues
Steps to resolve Sage 100 2019 unable to connect to server error:
Please recheck if the correct
IP address or server name was entered during workstation setup:
·
Browse to the
"..\MAS90\Launcher" folder on the workstation.
·
Open
the Sota.ini file.
·
Locate
the [Servers] section. The IP address or server name is listed after
the following text: "1="
·
If the IP address
or server name is incorrect, Enter the correct Server Name or IP address or
uninstall and then reinstall Workstation Setup
·
Verify the port is
open
·
Verify the IP
address or server name and port were entered correctly in the icon properties
Related Article: Sage-100-erp-error-65
If Port, Server Name, or IP
Address were confirmed accurate within side the above steps, this message can
arise if an Inbound Rule and Outbound Rule has now no longer been created for
the Sage 100 (previously Sage 100 ERP) port at the Windows 2008 or 2012 Server,
below Windows Firewall Advanced Security.
·
Open Administrative
Tools, Windows Firewall with Advanced Security console In the left pane of the
console, pick Inbound Rules
·
Right-click on pick
New Rule
·
Select Port click
on Next
·
Select Specific
Local ports and input the port quantity for Sage a hundred and click on Next.
·
Select Allow
Connection click on Next
·
Select Domain,
Private, Public and click on Next
·
Name the brand new
rule a call of your choice. Add an outline figuring out the guideline of thumb
is used for Sage 100 and click on Finish Create an Outbound Rule
following steps above.
Comments
Post a Comment