Hi All,   This isn't a serious issue or anything. But we've noticed that every time a user logs out of SAS EG (closes SASApp) or SAS Studio, the user receives an email from LSF Admin with CPU resource usage stats and job details along with the following error:   aklog: Couldn't determine realm of user:aklog: unknown RPC error (-1765328190)  while getting realm   Is this something we can control from SAS Admin perspective? By control I mean can we curb these alerts? Also what does the error message mean?    SAS Foundation : SAS 9.4 M5 SAS Studio : 3.71 SAS EG: 7.15 ... View more

Hi Members,   We use LSF with SAS. We recently upgraded to SAS 9.4 M5 and are currently testing it in our Dev environment. While testing, we came across a strange situation- We use the same LSF queue for Dev and Prod. But in Dev, we receive a notification the moment we log out of SAS Studio (sender id is the user who logs out@server name). The message is as follows: Job <Web Infra Platform Services 9.4 - SAS Studio Mid-Tier 3.7_SASApp - Workspace Server_*************> was submitted from host <abc.xqz.com> by user <mnop> in cluster <lsf1>. Then it gives the LSBATCH job summary (workspace process and variables) followed by resource usage summary.   The strange thing here is that since we are using the same queue and conf file for both Dev and Prod, I am not sure what setting do I have to check in order to stop these notifications.   I tried to add LSB_JOB_REPORT_MAIL=N in the workspace server script but no luck as of yet Has anyone faced this issue? If yes, then please let me know how to workaround this.   Thank you in advance! SK ... View more

Dear SAS Community,   I know that there are lot of tools available that do the job of monitoring your applications. For instance, you have sitescope that can monitor SAS Studio URL availability as well as the login mechanism. But I want to know if we can implement a script that does the same job? Something that does the following: 1) Open SAS Studio URL (<server>:<port>/SASStudio) 2) Enter credentials and login 3) Verify if the login is successful (either a HTTP 200 or by identifying the SAS Studio logo of the workspace etc.) 4) Log out 5) Verify whether the log out was successful (identify the "You have been signed out" message)   I know there are several ways to automate this, for example - use curl or java functions etc. But has someone implemented this? Can you please let me know how?   Thanks, SK ... View more

Hi All, I am currently running SAS 9.4 M3 enterprise edition and would like to know if I can upgrade only SAS Studio from v3.5 to v3.7? Please let me know your thoughts. Thanks. ... View more