Sage 100

I may just not have been aware of this, but is it typically required that the MAS 200 Application Server run as a Service when utilizing Terminal Services? I typically like to run it as an Application but on a recent 4.40 upgrade, was getting ""unable to connect to server. server is reachable, but it is not accepting..."". Once I changed it to run as a Service, that resolved it.

Had the same thing happen on a recent upgrade. Client was switching to total virtualization on all servers. MAS200 running as an application because they have 40-50 users logged in at one time but ran into same problem and had to switch to running as service.

BL, did you tweak the registery to allow the large number of users access?

Not sure. The client contact Sage Tech and they suggested running as a service. We we first tested it ran fine as application but as more people logged into MAS the connection issue came up. I was not there when they called Sage.

It may be that the session that's running the application logs off after you disconnect, where a service continues to run. I don't believe there's a console session to leave running. I would recommend running as a service in a virtualization environment.

Appears as though the cause was due to ""logging off"" the MAS 200 server (which does make perfect sense) - which obviously caused the Application Server to no longer technically be running.