You can set VERIFY_DEPLOYMENT to false in vars.yml to not perform these checks. Set the Pre-deployment Validation Parameters https://go.documentation.sas.com/doc/en/calcdc/3.5/dplyml0phy0lax/n1knvzbsifo9xqn1al0bh7wxrrkg.htm#p0fbpmc6e4n1kbn1jzx8fkejea5n ... View more

After you run the $objSAS definition, if you echo it does it have a listing for LanguageService? Do you see a SAS program running in the background? PS C:\Users\grwoot> $objSAS = $objFactory.CreateObjectByServer("Local",$true,$objServerDef,"","") PS C:\Users\grwoot> $objSAS LanguageService : System.__ComObject DataService : System.__ComObject FileService : System.__ComObject ODS : System.__ComObject Utilities : System.__ComObject Name : SAS Workspace UniqueIdentifier : 26C88ED3-72A2-4E78-933C-CB445314AB2B PS C:\Users\grwoot> ps |findstr "sas" 2397 38 15792 36568 1020 0 lsass 414 40 30600 35264 0.22 25648 1 sas PS C:\Users\grwoot> $objSAS.Close() PS C:\Users\grwoot> ps |findstr "sas" 2399 38 15888 36664 1020 0 lsass PS C:\Users\grwoot> ... View more

It looks like this code expects the .jpg and .txt files to be in that referenced path accessible to python, so if they aren't there I would not expect the code to work. ... View more

The documentation for migrating content from SAS 9.4 to Viya can be found in the link below. Migrating from SAS 9.4 https://go.documentation.sas.com/doc/en/sasadmincdc/v_046/calcontentmig9x/p0l66zxd87xa3nn1acb8scdcmhk2.htm More information specifically on promotion of authorizations can be found here: Content Migration - Authorizations https://go.documentation.sas.com/doc/en/sasadmincdc/v_046/calcontentmig9x/p0lui94y7l3fz5n1uzg6rgzgdyjy.htm#n05w20xb1i3xwnn187jgb3dgdfjb More information on promoting DI jobs can be found here: SAS Data Integration Studio Jobs and Transformations https://go.documentation.sas.com/doc/en/sasadmincdc/v_046/calcontentmig9x/p0lui94y7l3fz5n1uzg6rgzgdyjy.htm#p164nj8hy0bvyan0zb6x00zvba8b ... View more

Normally, when authenticating to the Metadata Server (as you would when logging in to clients), the supplied credentials are passed from the Metadata Server to the host for authentication by way of the sasauth PAM configuration. It would not use sudo to assume the user's identity as on the host, so it sounds like you may have a different PAM configuration on the test and staging environments. Check the contents of /etc/pam.d/sasauth. You can also test this outside of the clients using PROC PERMTEST and examine the sasauth logs to see what is happening. Using PROC PERMTEST to diagnose UNIX host authentication issues in SAS® 9.2 and later and in SAS® Viya® https://sas.service-now.com/csm?id=kb_article_view&sysparm_article=KB0036227 ... View more

Hi Nigel, I think this section is referencing if the section above it is not true (the VA.AutoLoad.Location is not accessible to the Environment Manager Enablement Kit server machine). i.e. DEFAULT is the VA.AutoLoad.Location. So if the path specified in the library properties under VA.AutoLoad.Location is not accessible from the SAS Environment Manager Enablement Kit server machine (the one with emi-framework, typically compute), then both of these (vafeed.destdir and AutoLoad.Location) could be changed to an alternate shared path, or if you mounted thee AutoLoad.Location to another path on the emi-framework host and then specify that path in vafeed.destdir, or point vafeed.destdir to some other path and have a regular process move the data to the drop zone. ... View more

sas-search is the microservice that facilitates the search function. sas-model-repository is used to manage models. sas-cas-server-default-controller is the CAS controller. sas-cas-control is the microservice that enables management of the CAS server through a REST API. ... View more

You may wish to engage with SAS Technical Support to review the authentication failure from the CAS side. ... View more

Right, when you run the SAS Deployment Wizard from your new depot it should go into Update mode. Here's the documentation on updates that goes through all the steps to prepare. The General Process for Software Updates https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/whatsdiff/n1c78q6tx3u0cfn1xrrusfynjrio.htm ... View more

Our deployment documentation covers OpenShift specifics here in the pre-installation tasks. SAS® Viya® Platform: Deployment Guide - Preparing for OpenShift https://go.documentation.sas.com/doc/en/sasadmincdc/v_046/dplyml0phy0dkr/p1h8it1wdu2iaxn1bkd8anfcuxny.htm ... View more

I usually apply all available hot fixes, but you would be specifically looking for available hot fixes for the component "SAS Web Application Server" in the SASHFADD report. Here's the links directly to those hot fixes for version 9.46 and 9.48 of SAS Web Application Server, I'm not sure which is deployed in your M7 installation as I believe this incremented mid-release. SAS Web Application Server 9.48 https://tshf.sas.com/techsup/download/hotfix/HF2/M3P.html SAS Web Application Server 9.46 https://tshf.sas.com/techsup/download/hotfix/HF2/I9U.html ... View more

You can see which hot fixes are installed using the ViewRegistry tool. Using the ViewRegistry Report and other methods to determine the software releases and hot fixes that are installed https://sas.service-now.com/csm?id=kb_article_view&sysparm_article=KB0036131 The SAS Hot Fix Analysis tool can take the output from this to determine if any updates are available. SAS Hot Fix Analysis, Download and Deployment Tool https://support.sas.com/en/technical-support/maintenance/hot-fixes/hot-fix-analysis-download-deployment-tool.html ... View more

The easiest way is probably to look at the running processes, i.e. ps -ef | grep tomcat. The tomcat release is updated through updates to the SAS Web Application Server component so would not be tied to your RedHat version but your SAS release (e.g. 9.4 M7) and if you have installed any hot fixes for the SAS Web Application Server. ... View more