We are using a 5 node grid environment with LSF 7.06, SAS 9.4, and Studio 3.5.  We have 1 non-clustered middle tier server with ~100 users signed in at any given time.  All servers are Windows VMs.  We use host authentication with Kerberos and users authenticate against one of our AD domains.  Since the beginning of this implementation, it takes us 1.5 - 3 minutes from clicking sign to getting into Studio. We already installed a LSF patch that allows for the LSB_JUSAGE_UPDATE=N setting in our lsf.config file, sacrificng job-level metrics for shorter login times, which were marginal at best.  I'll look into tweaking the mbd and sbd sleep settings to try and eek out a bit more speed, but I know we've already changed those values a couple times.  ... View more

I have a user getting the same error.  Just to add more detail, I've cleared temporary internet files, deleted and recreated the user's account in Metadata, rebooted, tried Chrome and IE, reset the security and advancded settings in IE to their default, checked for hung/running jobs for the user - none - and he still gets this error.  I've opened a track with SAS Support for this, and will reply here again if they provide me with a solution. ... View more

Thank you, Kurt.  All our SAS servers are Windows servers and I'm looking for testing SAS jobs, not processes.  You can establish a max jobs/queue or host within SAS GRID/LSF.  I'm increasing the max jobs or MXJ and need a test to prove that the change was effective. ... View more