Sage 100

Need some assistance with a client on MAS 200 version 4.50.4. They are all of the sudden receiving the attached connection time out error when logging on to MAS or when accessing tasks. Talked to Sage and they recommended opening ports 9000-10000 and then changings the user setting on the preferences tab in User Maintenance so that the ""Spawn Tasks from Application Server"" check is unchecked. When we do that, the user is receiving ""Connection failure to host: {tcp} 192.168.18.7; 5528 1;NODELAY;STREAM"". Any help is welcome!

Maybe something running on Port 10000. Veritas is a known culprit. See if they installed anything new on the server. Could also be a virus running on port 10000 as well.

We usually set them up to run on Port 9000 to avoid the Veritas Backup Exec conflict. You can also try running the service as an application on the server if the port change doesn't help.

If the MAS App Server is to run as a service, temporarily stop it and run as a desktop app. You may see server side errors otherwise not seen. For example I once discovered the service login account password had expired in Windows. Also: 1) Check App Server Config in the Server tab in the State section. See if any of the Disabled options are checked (see attached) 2) If Server 2008 or 2012 check if Windows Firewall enabled. If so there needs to an exception set (as an Inbound policy) for your App Server port. 3) As mentioned check if App Server port in use by another app. Keep App server stopped then run: netstat -a -p tcp Check Local Address column to have same port as App Server port

Thanks everyone. We discovered that the App Server running as a service was spawning close to 100 processes in Task Manager. We manually ended the majority of those processes and now are running as an application and all seems to we working now.

I'm waiting on a few answers from IT (including which users specifically are getting the ""Connection Timed Out"" errors) , but we have a 4.5.0.7 Sage 100 Adv client with 20+ users (mix of TS and non-TS) who recently upgraded from 4.05. Currently running as an ""Application"" but I may wish to try switching to a Service. @WayneSchulz, per your thread (https://90minds-com.socialcast.com/messages/17828841), do you recall if you ended up having to do anything further with the Timed Out errors besides switching to a Service? I'm also wondering if the CS ODBC functionality is causing a conflict somewhere because we had enabled that prior to implementing TS to speed up Crystal forms and reports printing. I figure we can now turn that off at the server level, or at least turn it off in User Maint for the users who now connect via TS. ?? (""windx client connection: connection timed out waiting for your application to start. Please contact your administrator, as there may be a configuration error on the server. The server side process failed to start or respond."")