The problem in that KB article was fixed in M8. ... View more

Hi @drahorg .  Good question.  I was not sure of the answer, so I did a little trial and error testing with the sas-viya CLI and the audit plugin to look at the audit records.   First I changed the sas.audit.record/audit.recording.level property to DISABLED, and then changed it back to the default, LOW.  I didn't find anything useful using sas-viya audit list, so then I used sas-viya audit list-activities, which queries the activity records, which are the newer revamped audit records.  Here is what I found:   [root@hostname scripts]# ./sas-viya audit list-activities --user-id sasboot --after 2025-04-15T00:00:00Z --resolve-uri ID Time Stamp Action State User ID Application Administrative Action Object Name Object Type Service Name URI User Interaction Secure 8cb7c469-2613-4672-80a8-d2585efe64a5 2025-04-15T12:29:19Z update success sasboot true sas.audit.record Configuration configuration /configuration/configurations/9a8435d5-06ca-4d04-b888-574d9d925372 true b1615f7b-a6af-4baf-90cb-9edd274fb7e7 2025-04-15T12:32:39Z update success sasboot true sas.audit.record Configuration configuration /configuration/configurations/9a8435d5-06ca-4d04-b888-574d9d925372 true   So this tells me that the sas.audit.record (Object Type) property was updated (Action).  It tells the time and who did it.   What it doesn't tell me is that audit.recording.level property was changed nor does it provide the before and after value.  I did a similar test by changing sas.audit.record/activity.recording.level and the results were similar.  I also chose a few other random services to make configuration changes on and get similar results.   [root@trck1015055 scripts]# ./sas-viya audit list-activities --user-id sasboot --after 2025-04-15T00:00:00Z --resolve-uri ID Time Stamp Action State User ID Application Administrative Action Object Name Object Type Service Name URI User Interaction Secure 8cb7c469-2613-4672-80a8-d2585efe64a5 2025-04-15T12:29:19Z update success sasboot true sas.audit.record Configuration configuration /configuration/configurations/9a8435d5-06ca-4d04-b888-574d9d925372 true b1615f7b-a6af-4baf-90cb-9edd274fb7e7 2025-04-15T12:32:39Z update success sasboot true sas.audit.record Configuration configuration /configuration/configurations/9a8435d5-06ca-4d04-b888-574d9d925372 true c394d979-e78e-4745-beaa-495d81e7c82f 2025-04-15T12:34:45Z update success sasboot true sas.identities Configuration configuration /configuration/configurations/4fbf97b7-7953-4dfe-bd32-083fed73d2c4 true ace2940e-e6e4-4629-8791-030e7622e45e 2025-04-15T12:36:38Z update success sasboot true sas.identities Configuration configuration /configuration/configurations/4fbf97b7-7953-4dfe-bd32-083fed73d2c4 true 1f564a09-b7e3-498e-b66f-f2381656f5cd 2025-04-15T12:36:58Z update success sasboot true sas.logon.initial Configuration configuration /configuration/configurations/d436d15e-019b-40d5-88fa-c923902d642b true c755989c-774f-44e8-81d7-b8c807cee834 2025-04-15T12:39:16Z update success sasboot true sas.logon.initial Configuration configuration /configuration/configurations/d436d15e-019b-40d5-88fa-c923902d642b true 3dee5e93-5cbf-4e88-a271-52aeb823f482 2025-04-15T12:39:44Z update success sasboot true sas.notifications Configuration configuration /configuration/configurations/14690a99-71ad-425c-98c4-ca417fd645d4 true 725ce1a4-ec1a-477b-ae21-d8425cbb3cf6 2025-04-15T12:39:57Z update success sasboot true sas.report.service Configuration configuration /configuration/configurations/9516f56a-4641-41d1-aca7-a672b8e17859 true 3054e259-8073-46df-81ea-1efc42e061fa 2025-04-15T12:40:24Z update success sasboot true sas.report.service Configuration configuration /configuration/configurations/9516f56a-4641-41d1-aca7-a672b8e17859 true f42202ed-79c6-48ab-a11e-4436fbb67334 2025-04-15T12:40:32Z update success sasboot true sas.notifications Configuration configuration /configuration/configurations/14690a99-71ad-425c-98c4-ca417fd645d4 true 4f718d3a-4ba7-480b-9480-976b7d473fdd 2025-04-15T15:32:07Z update success sasboot true sas.audit.record Configuration configuration /configuration/configurations/9a8435d5-06ca-4d04-b888-574d9d925372 true af50333b-233c-45ab-9bc5-4bab3dffea01 2025-04-15T15:37:03Z update success sasboot true sas.audit.record Configuration configuration /configuration/configurations/9a8435d5-06ca-4d04-b888-574d9d925372 true   I also used fulljson output and the --details options, but did not get the additional information that you are asking about.   While this does not completely meet your needs, it does help you know who modified a configuration definition and when.  I will check to see if we have any open feature requests to have more detail included.   For more information about querying audit records, refer to https://go.documentation.sas.com/doc/en/sasadmincdc/v_062/calaudit/n1medruepeq0wzn19tv45t84j47j.htm ... View more

The SAS installer account is not managed by the SAS Deployment Manager.  Changing its password on the host or domain should not impact SAS.   The lsf and pm account passwords cannot be changed with the SAS Deployment Manager.  I am unfamiliar with the steps for updating those passwords.   If you don't get an answer here, you can open a case with SAS Technical Support. ... View more

Hi @DJWanna .  Passwords that are stored in the SAS configuration can be managed using the SAS Deployment Manager 'Update Passwords' task.  For instructions, refer to:  https://go.documentation.sas.com/doc/en/bicdc/9.4/bisecag/n0rze9kvk0b7b0n16r2dsvfuq14r.htm ... View more

You can try to stop the agent, delete the SAS-configuration/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/data directory and then restart the hq-agent.   If that doesn't work, you'll probably need to open a ticket with TS and provide the agent log. ... View more

You don't need to reboot.  Just rename the file and hit Retry on the SAS Deployment Wizard. ... View more

There is not enough information in your screenshot to help.  The screenshot links you to a log file where you will find more information about the cause. You can search the log for "build failed" and/or "caused by" to try to get to the relevant part of the log. Depending upon the nature of the error, you might also need check the Metadata Server log at c:\sas\configmeta\lev1\sasmeta\metadataserver\logs Additionally, you might want to open a case with SAS Technical Support. ... View more

Just to clarify, what you are referring to in SASServer2 is an application sometimes referred to as "SAS Environment Manager Midtier" or "SAS Environment Manager Administration".  To access this application, you log in through the traditional SAS Environment Manager UI and then select the Administration tab.  That launches another web application in a new window.  That application is what is running in SASServer2.  While seemingly embedded within SAS Environment Manager, they are separate applications running in separate application servers.   For reference, this SAS Environment Manager Administration:  SAS Help Center: Using SAS Environment Manager 2.6 Administration ... View more

How are you confirming the services are down on the middle-tier?  The SAS Environment Manager runs a separate Tomcat server that is independent of the SAS web applications servers.     SAS Environment Manager does authenticate using SAS Logon Manager which runs in the SASServer1_1 web application server, so if SASServer1_1 is down, I would expect the SAS Environment Manager logon page to be unreachable.   You can check the SAS Environment Manager logs at <sas-config>/Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/logs (boostrap.log and server.log) to see if it's running or not. ... View more

Hi, The User Activity report is in the /Products/SASEnvironmentManager/Dashboard Items path in SAS Content, which has a rule conditionally prohibiting Authenticated Users from seeing it. You will need to modify the condition of this rule to include a group this user is a member of, or call them out specifically. For instance by replacing this:   !groupsForCurrentUser().contains('SASAdministrators') && !groupsForCurrentUser().contains('sasapp')   with this:   !groupsForCurrentUser().contains('SASAdministrators') && !groupsForCurrentUser().contains('sasapp') && !groupsForCurrentUser().contains('NewGroup')   or:   !groupsForCurrentUser().contains('SASAdministrators') && !groupsForCurrentUser().contains('sasapp') && !currentUser() == 'userid'   General Authorization: How To (Rules page) https://go.documentation.sas.com/doc/en/calcdc/3.5/calauthzgen/p1bh4gj8c2xv1nn1fx011prusmii.htm   The User Activity report uses the SystemData.Audit CAS table which Authenticated Users by default does not have permission to see, so the user/group will need to be granted permission on the SystemData caslib as well.   CAS Authorization: How To (Authorization Window) https://go.documentation.sas.com/doc/en/calcdc/3.5/calauthzcas/n10ey3zz0qwxrsn0z6l25qo310q7.htm ... View more

@eddieleung305 - Thanks for pointing that out!  I overlooked the note above the linked html files.     (I deleted my previous reply to not cause confusion) ... View more

Hi.  Thanks for sharing.  I wanted to point out one clarification.  The data in the SystemData.AUDIT table does not come from system or application logs.  That data comes from audit records that are stored in the SAS Infrastructure Data Server (PostgreSQL database).  When a user performs some action against a service, that service might create an audit record for the action.  The audit record might be recorded in the database by the audit microservice.  A job runs every two hours to extract the audit records from the database and load them into SystemData.AUDIT.     As for the example where audit data about reports being read not showing up, that is because, by default, the audit microservice does not record report "read" actions.  The reason for this is due to the volume of audit records that can be generated.    More information about the auditing can be found here:  SAS Help Center: Auditing: Overview ... View more