SAS EG 7.15 HF8 - having issues in using Disconnect button for workspace servers

[sandeeppajni1]

Hi,

We have been facing issues in SAS EG 7.15 HF8 where people when connect to more than one workspace server and try to use Disconnect button to disconnect from the workspace servers, the SAS EG session freezes. Has anyone else faced a similar behavior and if any suggestions can be provided?

[SASKiwi]

@sandeeppajni1  - I suggest you open a track with SAS Tech Support as this is likely to require turning on EG's application logging which STS can diagnose.

[sandeeppajni1]

@SASKiwi, already raised it with support, this is being investigated

[JuanS_OCS]

Hi @sandeeppajni1 , good to see you here!

@SASKiwi , everyone, just for additional information/background, let me add the following.

This is a SAS Grid Manager environment, SAS 9.4 M6, with SAS Provider (the new grid with SAS Workload Orchestrator), based on RHEL 7.6 servers. 

We identified a bit of slower connections to the SASApps through SAS EG than usual for single SASApp connections or for Grid environments based on LSF. This slowness was more pronounced in the past but now it is almost OK. The speed is visible also during disconnections. We also identified that this slowness is produced due to the combination of this new grid making multiple authentications at the same time (this is what has been optimized already to a certain degree), and the AD authentication being slow specially when retrieving groups (which is an infra issue for Linux servers).

Of course it might be unrelated, but I have a theory that this is related to those a bit slower connections, and the combination of Integration Technologies and this SAS EG version that cannot handle completely well those slower connections than usual.

I would like to mention as well that the main issue is not the impossibility to disconnect from SASApps, but the fact that when it happens, SAS EG freezes with the wheel of death and users can only pass through it by restarting SAS EG. Which is quite frustrating for several of them, who need to switch SASApps often.

I hope it helps.

PS. Indeed, the issue is with SAS Tech Support for a year or so. Our contact is providing us great support, not only with this one, but with other important items as well.

Best regards,

Juan

[SASKiwi]

@JuanS_OCS  - Good to know the background to this issue. Does the same problem happen with EG 8?

[JuanS_OCS]

@SASKiwi we would like to know that one too. In certain business/companies you cannot apply changes or test things that easily once things are in Production, due to general practices and bureaucracy. We will get there, in time...

For now we know that with the SAS EG 7.12 that was applied to the old environment this particular issue does not ocurr.

We will start by installing the latest HFs for SAS EG 7.15 and Integration Technologies, in the DEV server. Let's see how it goes.

[JuanS_OCS]

An update, @sandeeppajni1 , @SASKiwi 

So it seems the latest HF for SAS Integration Technologies resolves the issue. This is being tested as we speak.

[sandeeppajni1 · Accepted solution]

Indeed, the installation of latest hotfix for Integration Technologies Client (E2F005) (both 32 and 64 bit versions together in the 64 bit OS machine) did the job!

Thanks to @JuanS_OCS