Sage 100

Trying to get CSODBC working (version 2013). Test connection fails. Telnet can't open the port. On Windows 2008 R2 Standard server, how do I find out the port status - which ports are open, available? This is our internal server, by the way.

in a cmd window ""netstat -a"" will provide a list of the ports currently in use. If Windows firewall is on, most ports will be blocked unless you open them in the firewall.

in 2008 R2, opening a port is done by creating a new inbound rule

I just had to create an Inbound Rule recently: On the Windows 2008 Server, on the Administrative Tools menu, select Windows Firewall with Advanced Security console. In the left pane of the console, select Inbound Rules. Right-click, and select New Rule. Select Specific Port. Select 10000 or the actual port number for Sage MAS 200. Select Allow Connection. Click the Profile tab, and select Domain, Private, Public. Name the new rule MAS200 or a name of your choice.

Does it work on the server? Check user name to make it is enabled.

Thanks! Creating an inbound rule did it.

I was speaking to Chris Powers from SAGE about this. On V2013 there is no user limitation so he recommends using the CSODBC on Advanced if there are any speed issues printing from clients.

Good to know.

FYI - I have one installation where I enabled everyone to use the CSODBC and they are getting random issues with the service stopping. Sage at this point has no idea why this would be happening. So just be on the lookout. But it does address speed issues where there are subreports and does address the perforrmance in AP CHeck printing. And FYI - the AP check printing performance - the issue is the subreports causing it to go SLOW. What I have done on some of my installs is delete 2 of the sub-reports in the AP check form.

One out of how many. I haven't installed any yet.