Hi Hemasai98,   I see the below message in SASStudioMidTier3.8.log after i hit the SAS Studio URL:   2019-12-26 12:50:51, 760 [Finalizer] WARN [unknown] com.sas.services.connection - (fE3,r0) A connection was returned to the factory by the garbage collector (fE3,c0) ... View more

Hi hemasai98* ... View more

this is not first time we are accessing. we were able to access SAS Studio till Dec 2nd and i did updated SAS Server order from SAS 9.4 M6 19w7 shi event to 9.4 M6 19w47 ship event order. then SAS studio issues started with sluggish response from Dec 3rd. ... View more

Hi hemaSASi98,   I did check that all 3 SAS WebAppServers are running.  ... View more

its same behaviour on Firefox, IE browser too. ... View more

Hi Jakarman,   I am running with similar issue.   I have set up SAS library(abc) in SAS SMC for oracle schema. This schema name called ‘ABC’ in Oracle server database(port opened and updated tnsnames.ora with path name details).   Created user group with ‘OraAuth_ABC’ domain added old schema user name and PW then added users. Path name been defined in server connection and selected OraAuth_ABC domain for authentication field. Library created : schema name added,  selected the oracle connection and selected the username(OraAuth_ABC) for authentication.     Last week I have create another SAS library(xyz)  for different schema called ‘XYZ’ (same tables for more data) which exist in same DB server same as above and domain:‘OraAuth_XYZ’ and different user id and PW for XYZ schema.   Users are able to access data from both abc and xyz libraries using SAS data and proc steps when users explicitly referred abc.table or xyz.table library names.     Issue: when users run pass through code to read from XYZ schema, the data is pulling from ABC schema.   If users access table from SAS Data step and Prod step by referring libref xyz.table then the data is coming for 201611 and 201612.   When user run pass through code for  201611, 201612 and 201701 data, as below code  result is 0 records which means its pointing to old abc schema.   Pass through code for Last week set up library:  proc sql; connect to oracle as edw(AuthDomain=OraAuth_XYZ   path=Path); create table test as    Select * from connection to xyz           (select  distinct(ID)  from table Where date=201611); disconnect from xyz; quit;     is this default behavior? why the above code is point to old schema table? am i mssing anything? shoudl i need to mention schema name? ... View more

Hi,   Tha clients are in Windows machine and can connect to SAS Prod Environment successfully. the Issue to connect TEST SAS Environment.   I have enabled Log for EG and Workspace server and attached as well for your reference. ... View more

I am able to connecto SAS Prod SAS Servers environment, no issues on that- so no changed made in OS level.   The issue is only to connect SAS Test environment, not able to access/exoand SASApp in EG, but i can connect to SAS Metadata Server.   Thanks, Ram ... View more

Hi SASWiki,   I mean we have 2 SAS Environments called Prod and Test with completed separate machines.   Users can connect to SAS Prod environment and run the programes successfully, but not to SAS Test Environemnt.   I can Launch workspace server using user account in Putty session, tested telnet test to compute server machine name on 8591 port, tested integration technologies test to workspaveserver on 8591 port. everything working fine exept unable to access Server > SASApp in EG.   Thanks, Ram ... View more