The audit functionality is how Viya would surface this information. The sasuser.viya directory is used by the compute server started when using SAS Studio, so would not apply to any user logging into the system. If your LDAP server logs bind attempts you might be able to capture the information from there. ... View more

You can create rules to limit access to functionality in the various applications: Access To Functionality: Application URIs https://go.documentation.sas.com/doc/en/sasadmincdc/v_068/calatf/n0o6xx292jn2jmn1pnj3s3oqcebw.htm The /dataPreparation_capabilities/exportTable URI controls the ability to download a table. Limit Access to the Download Table Option: https://go.documentation.sas.com/doc/en/sasadmincdc/v_068/datahub/p0m6sdzan2fadwn1d9hiiyu18i49.htm#p0nokj409ak0fvn1nxg1vzact5xs In SAS Studio, there is a configuration option toggle "allowDownload" to limit the ability to download. studio - allowDownload https://go.documentation.sas.com/doc/en/sasadmincdc/v_068/calconfigref/n1gummgwr982rsn1ffv0aq4ma88x.htm ... View more

In looking at my M7 environment I don't see a SAPHana driver path there, are you sure that wasn't added post-deployment? ... View more

You should check the logs for saslogon to see what failure is causing the HTTP 500 response. ... View more

The log content provides is saying that when trying to run the task to load the content to the SAS Content Server, the task failed. It looks like it failed on the initial connection to the SAS Content Server rather than when actually loading any content. I would suspect then an issue with the SAS Content Server web application or one of its supporting services on SASServer1_1, or an issue with the Metadata Server, so I would check those logs for more information. ... View more

When you access SAS Studio and have not yet authenticated, SAS Studio would redirect you to /SASLogon to authenticate. From the URL there it looks like /SASLogon is being appended to the URL repeatedly through subsequent redirects, so this is probably a configuration issue either in the SAS Web Server or SAS Logon. A Technical Support case would be appropriate to review your configuration. ... View more

In Viya 3.x, the Launcher Server is the process that starts the compute server process. This error message means that the Launcher service could not establish a connection to the Launcher server. You should confirm the Launcher server is running (sas-viya-runlauncher-default) on the compute server host, and ensure your Viya deployment is up to date. ... View more

Does this error occur while the SAS code is running or is it preventing the SAS session from starting at all? SAS is provided a WORK option on startup specifying a parent location (e.g. /tmp). SAS will create a WORK library within that path specifically for it's process (e.g. /tmp/SAS_workFFFFFFFFFFF_hostname) If the parent path specified by the WORK option is not accessible, SAS will fail to start with an error: $ ./sas -nodms -work /tmp2 ERROR: Library WORK does not exist. NOTE: Unable to initialize the options subsystem. ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED. ERROR: Unable to initialize the SAS kernel. If SAS is running and some process deletes the WORK directory it created, you'll see this error in your code execution: ? data test; x=1; run; ERROR: Library WORK does not exist. NOTE: The SAS System stopped processing this step because of errors. So, if you have some process set up to clean your WORK path periodically, it could be deleting your WORK directory from under you, causing this error. ... View more

If the pod did not restart then the liveness probe didn't fail enough to trigger this, suggesting the failure was not ongoing. For sas formats the liveness probe by default is queried every 20 seconds, and if it fails three times the service is restarted. So it sounds like whatever the issue was, it did not last more than 60 seconds. ... View more