@MariaD,   The password from the metadata cannot be decrypted. ... View more

@nhvdwalt,   Depends on what you are using. If you are using MIT Kerberos for authentication, instructions are provided in the deployment guide to run the ksetup command to acquire tickets for client machine from the correct Kerberos realm.   If you are using Active Directory only for authentication, no additional configuration is provided in the deployment guide. Instead, your Kerberos administrator can refer to the SAS In-Database Products: Administrator's Guide for more information. ... View more

@nhvdwalt, Yes. Let me know if you have any questions about the configuration. ... View more

@MariaD,   You checked everything. If you want to investigate a problem further, I would suggest opening a technical support track. Send to me the number, if you decide to do so. ... View more

@MariaD,   If you are absolutely sure that you have installed all the packages that required for SAS installation, launch the setup.sh script with the -skiposlevelcheck option. ... View more

@MariaD,   Please send an output from the following command:   swlist -v | grep -i atomic ... View more

@pkatapally,   There is not a way to tell you exactly what happened without some diagnostic logging turned on when the failure occurred.   Usually, the failure is due to file permission errors.  If logging for the WorkspaceServer sessions has been enabled, this is a common source of failure if the users are not able to create the logs due to permissions on the directory holding the logs.   Other sources would be incorrect permissions to create the WORK library, or, especially in the case of new users, their Unix $HOME directories do not have the correct permissions.   One last cause would be that the permissions on the directories in the <SASConfig> path have been set so that the users are not able to access and execute the WorkspaceServer.sh script. ... View more