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

The main part of the error is:   [echo] ApplicationMetadataUtility has failed. Application Solutions Svc Data Tier 5.61 already exists. [echo] Return Code: 8   This indicates that SAS Solutions Services Data Tier has already been configured and cannot be configured again.  If you previously had a failed configuration and did not remove the failed configuration, you'd get this error.   ... View more

There are no standard plan files that will deploy Grid. As already mentioned, for this deployment, you must contact your SAS account team to have your custom plan file created. ... View more

Hi. You are correct that SAS provides the plan file. Customers cannot create this. You will need to contact your SAS account team. ... View more

Additionally, here are a couple of papers that might help shed some additional light on the migration and promotion processes for you:   Latest and Greatest: Best Practices for Migrating to SAS&reg; 9.4 -this paper mentions going from 9.2 or 9.3 to 9.4, but the same concepts apply for 9.4 to 9.4 migration.   Getting the Latest and Greatest From SAS® 9.4: Best Practices for Upgrades and Migration ... View more

Hi.  Since you are moving from one server to another, an in-place update of the software will not be possible.  Your two options are: 1.  Perform a migration using the SAS Migration Utility and the SAS Deployment Wizard 2.  Perform a new out-of-box deployment on the new server and then use the SAS Promotion Tools to move over selected metadata and content.   Migrating a SAS deployment is not a trivial task, so you will not find a video or quickstart guide for walking you through the process.  I suggest you read the Introduction section of the SAS 9.4 Migration Guide which can help you decide if migration or promotion is best for you.   SAS Help Center: Approaches for Upgrading to SAS 9.4 ... View more

For the Text Analytics Document Conversion Host prompt, instead of specifying the actual machine name where you are recording the response file, you could try specifying "localhost" or "127.0.01", both of which should resolve to the local machine where SAS is being installed.   ... View more