Sage 100

When trying to start Sage 100 ERP Advanced 2014 from a workstation I receive the message, ""Unable to connect to server: ""SEVERNAME"". The server cannot be found."". I can access the server just fine. The installation was done across the network, with no errors. I can Ping the server. I have uninstalled and reinstalled many times. Tried it with IP address instead of server name, tried on other workstations. The service is running on the server and we can run Sage on the server without a problem. The problem appears to be that the port is blocked, but I can't figure out how. We've turned off any firewalls or anti-virus. I'm using port 9999,(have tried others). Running portqry on the server for that port answers LISTENING, portqry run on the workstation to the server answers FILTERED. The entire 9000 range answers FILTERED. I'm logged in as the administrator. I don't know what else to try. ***Update*** I ran netstat and the PID for port 9999 was 1184. Task Manager shows the Sage service running with PID 1184. The program works on the server and netstat and portqry show port 9999 LISTENING, it's just when I try to access it from any other machine that I have a problem.

If port, ServerName, or IP address have been verified correct in the above steps, this message can occur if an Inbound Rule and Outbound Rule has not been created for the 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 port number for Sage 100 ERP and click Next. Default port is 10000 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 ERP and click Finish 9.Create an OutBound Rule following steps above.

We've seen this also. Make sure Windows Firewalls are off. We also had this error on a terminal server where the licensing wasn't per user. Also solved this on individual workstations by adding individual workstation IPs to Symantec Endpoint Protection Intrusion Prevention.

On the server, go to a command-line and type: netstat -aon | find "":9999"" The last column should give you the Process ID (PID) of the program that's actually using port 9999. You can then use Task Manager (if you don't see the PID column, go to View \ Select Columns and check PID) to make sure that it's the MAS service account that actually has that PID. It sounds like something else may be stealing 9999.

Will give these a try and post an update. Thanks all.

I ran netstat and the PID for port 9999 was 1184. Task Manager shows the Sage service running with PID 1184. The program works on the server and netstat and portqry show port 9999 LISTENING, it's just when I try to access it from any other machine that I have a problem.

Then there must be some other firewall (or antivirus) running on the server, or maybe port blocking at the switch level (that's pretty rare).

I have had the same issue and it's always been resolved by setting up the Inbound and Outbound Rules on the server.

Are the permissions for the users on the Sage Share set correctly?

My client is trying a new IT company and they found a DNS issue and some clean up that needed to be done in the Active Directory. They're going to fix those issues and take a good look at the set up on the server and network and fix any other issues they find and then we'll see if that fixes my problem. We'll see how it goes!