Sage 100

On site 100 advanced version 4.4 30 users... frequently receiving ""WindX client connection: Connection Timed Out waiting for your application to start"" on the workstation. Server is Win Server 2008 R2. Read KB SS3003-ABC article but pertaining to modifying the registry. Article is unclear as to optimal registry settings. Has anyone seen this before? What was done to correct it?

Yes and either (a) ran as application or (b) made registry changes outlined in the SS3003 article

Agree with Wayne, its easier to run it as an application than mess with windows heap size etc.

Already running as an app. Increased the heap size last week to 20,480 and no help.

Another thing to check is on each user in User Maintenance make sure Spawn Tasks from Application Server is checked

They all have the spawn task box checked.. I just verified. What does the ""low speed connection"" check box do? I know it is used for remote connections, but does checking it conserve server resources in any way?

Sorry, not sure @ low speed connection but I have not needed to use that for this issue. Ia m out of ideas for you, you may need to get Sage involved.

Thanks for your suggestions Wayne and Bruce. I called Sage and they passed it off as a Microsoft issue... not enough server resources... that is the extent of the help they will provide... particularly since 4.4 is no longer supported. In the process of upgrading to 2014 on a new server but wont go live for a month or so...

See also Alnoor's tips - http://www.s-consult.com/2008/10/08/tips-how-to-set-up-an-application-server-in-sage-mas-200-version-4x/

Thank you Wayne. Great tips.