Hi @afa1  Was your playbook created using the current sas-orchestration?  The current version of sas-orchestration is 1.21.9. See steps 5 and 6 of SAS Help Center: Adding SAS Viya Software to a Deployment and Upgrading Products in SAS Viya 3.5    ... View more

Hi @afa1  From the rabbitmq 3.13 it looks like you are using a new Viya 3.5 24w44 order. With a new Viya 3.5 order make sure to run site.yml instead of update-only.yml.  It can be confusing so I'm sharing some information that I hope you find helpful.    For the case where you have SAS Viya 3.5 deployed then get a new Viya 3.5 order, you want to use the instructions here which use site.yml: SAS Help Center: Adding SAS Viya Software to a Deployment and Upgrading Products in SAS Viya 3.5   You will only use update-only.yml for the case where you want to install updates/hot fixes with your existing order.  SAS Help Center: Updating Your SAS Viya Software You might also find this new section of the deployment documentation helpful.  SAS Help Center: Planning for Extended Standard Support               ... View more

Hi @ronnynch   You would still take the approach in option A which is to clone your server to a new machine. Then on the new machine run the SAS Deployment Manager Update Host Name References tool to update your SAS deployment with the new machine name.  The idea is that SAS doesn't support restoring a backup of just the SAS installation and configuration directories to a new machine.  If you want to restore a backup of your server to a new machine, that has to be full system images like what is defined in option A of the SAS Disaster Recovery Policy as an exact clone.  The requirement for an exact clone also applies to using the Update Host Name References tool on the new machine.  See Use Case 2: One or More Servers Have Been Cloned to New Machines SAS Help Center: Overview of Updating Host Name References       ... View more

Hi @ronnynch  I would recommend starting with the SAS 9.4 Disaster Recovery Policy which explains the supported options for recovering SAS content.   https://support.sas.com/en/technical-support/services-policies/disaster-recovery-policy.html If you are planning to use the SAS Deployment Backup and Recovery Tool for recovering content, that is supported only when using Option A in the policy and the machine names of the target system must be the same as the machine names used in the deployment of the production (source) system.  The requirement about the machine names is discussed in the in Limitations and Considerations section of the policy.  After you have restored and validated the target system, if you want to change the machine names for the deployment on the target system, look at Update Hostname References with SAS Deployment Manager SAS Help Center: Using the SAS Deployment Manager to Update Host Name References  ... View more

Hi @jbond007    When preforming a restore to alternate deployment, there are three shared vault locations. 1. Source shared vault - the shared vault of the source deployment that has the Viya backups from the source deployment. 2. Target shared vault - this shared vault of the target deployment. This is the shared vault location you setup for the target deployment. This would have backups from the target deployment. Remember you need to test backup and restore in the target deployment as a prerequisite.  3. Alternate shared vault - this is the shared vault location you create just for the purpose of restoring a backup to alternate deployment.    Restore to alternate deployment requires you create an alternate shared vault and that's true regardless of what method A or B you plan to use.     You then copy the contents of the source shared vault to the alternate shared vault.  Then if you are using Method A you then edit the backup configuration using SAS Environment Manager and set the sharedVault property to be the location of the alternate shared vault.  After you do that you should see your backup from the source system when performing step 4 of Method A   sas-admin backup list If you have further questions, I recommend opening a case with SAS Technical Support.  ... View more

Hi @thesasuser  That error message you see in SASStudioV when SAS Viya is deployed on Windows is commonly seen when the user's browser is not configured for delegation of Kerberos credentials. I'm not sure what browser they are using but if Microsoft Edge or Google Chrome have you already asked the user to verify that policies AuthServerAllowlist and AuthNegotiateDelegateAllowlist are set and have the correct hostname?  You could ask one of the users who is having the problem to check their browser policies by entering:  edge://policy/ chrome://policy/   The configuration for Microsoft Edge and Google Chrome to Use Kerberos and the other browsers is in the SAS Viya 3.5 Administration guide here:  https://go.documentation.sas.com/doc/en/calcdc/3.5/calauthmdl/n1pkgyrtk8bp4zn1d0v1ln4869og.htm#n1aqnjfd7x8c5sn1pdpk5zzpqo2d ... View more

Hi @pururshothaman,    The process for removing a CAS worker is documented in the SAS Viya Administration Guide.  You could follow most of what is documented there except of course steps that involve logging into the CAS worker given the VM was deleted. SAS Help Center: Remove CAS Worker Software.  ... View more

Hi @Nigel_Pain    To see if the SAS 9.4M7 software you have installed has a requirement for .NET the best place to check will be the system requirements documentation. Search | SAS Support It's possible that the .NET installed on the Windows server that is your SAS Middle Tier is for something other than your SAS software, for example .NET is required for Windows PowerShell.  The .NET 4.8 on your Windows servers for metadata, compute, LASR would come from the requirement for SAS Foundation on Windows. You can find this note in the Software Requirements section of System Requirements--SAS 9.4 Foundation for Microsoft Windows for x64 "SAS software requires the Microsoft .NET Framework, which SAS provides as a convenience. SAS obtains the latest version of .NET as a system redistributable from Microsoft when preparing SAS software for release."  Some SAS clients also require .NET, for example SAS Enterprise Guide.  You can look at the <SAS software depot>\install_doc\<order>\ordersummary.html to see what .NET version was provided in your 9.4M7 order and that will be a .NET 4.8.    If you still have questions, I recommend opening a track with SAS Technical Support. ... View more

Hi @sathya66,  For this other error I recommend you open a track with SAS Technical Support.    ... View more

Hi @sathya66    It looks like you selected HTTPS as the protocol for the SAS Web Server but the step to add your certificate was missed before running the SAS Deployment Wizard to configure with the plan file.  Here is a link to a SAS note with the error you encountered:  52099 - The SAS® Web Infrastructure Platform load-content stage fails in SAS® Deployment Wizard when you use a generated Secure Sockets Layer certificate   When performing a new deployment, if you will be choosing HTTPS as the protocol for the SAS Web Server in the SAS Deployment Wizard you would first run the SAS Deployment Wizard to install only with your plan file.  Then run the SAS Deployment Manager to add your certificate. Then run the SAS Deployment Wizard to configure only with your plan file. You can find information about this here SAS Help Center: Install and Configure SAS Interactively.    If you have questions, please open a track with SAS Technical Support.  ... View more

Hi @sasviyaLC    Using the group name 'sas' is a requirement. You cannot use/assign an alternative name for this group. For more about this requirement see User and Group Requirements in System Requirements of the SAS Viya 3.5 Linux Deployment Guide. SAS Help Center: User and Group Requirements     ... View more

Hi @venkatviswanath,    For SAS 9.4 refer to the SAS 9.4 Administration documentation here: SAS Help Center: Using the SAS Deployment Manager to Update Host Name References.  Pay attention to the requirements in the documentation when cloning a server to new machines. A copy of just the SAS deployment is not supported.  When the document is talking about transferring full system images that is the same as approach A here Disaster Recovery Policy | SAS Support        ... View more