I recently did UIP from M7 to M8 with TLS/SSL enabled and I did not give much attention to this step and my UIP went with no issues. I used to worry about this in older maintenance releases, M0, M1, M2 etc...   As @kumarsandip975  mentioned, just verify that your TLS/SSL RootCA and any IntermediateCAs for your environment are already imported into SAS cacerts. if you wanna be extra caution, when you first do UIP for SASHome, run SDM and import your TLS/SSL files, then run SDM and choose "Update Existing Configuration".   Some notes I have about UIP: 1. follow the knowledge base number KB0036368. 2. During UIP process, after updating SASHome, exist second phase of the Wizard when it asks to select SASCONFIG for update and run SDM manually instead, and choose "Update Existing Configuration" for two reasons:   a. the machines I had were using alias names and SAS Wizard does not pass alias names to SDM in the second phase when it launch SDM automatically for you to update SASCOFIG  b. SAS wizard consumes lots of memory and tmp space so not to face a crash I stop the Wizard on SASCONFIG update phase, then I run SDM manually instead to update SASCONFIG.   On Mid-tier when I ran SDM manually I also used the javaoptions parameter to increase SDM memory size from 2GB to 4GB because it failed on first run (mid-tier SASCONFIG update consumed SDM default allocated memory of 2GB):   /opt/sas/sashome/SASDeploymentManager/9.4/sasdm.sh -javaoptions "-Xmx4096M"   3) Make sure that /tmp has at least 10GB free, preferred 20GB especially for Mid-Tier. 4) Make sure that you have enough free memory - I first stopped SAS, rebooted Linux and then started SAS to free memory buffer/cache 5) Make sure disk space is about 1.5 of SAS size - i.e: if SAS is installed in /sas directory and SASHOME and SASCONFIG are consuming 20GB, then you would need at least 30GB (20x1.5) of available disk space inside /sas directory   UIP does not upgrade SAS Internal database (PostgreSQL) automatically, so SAS PostgreSQL keeps to be the old version after UIP finishes. For that check SAS online documentation to verify your Postgresql version and on how to upgrade it.   ... View more

Hi @Amitkum2 ,   I do agree with everything @JuanS_OCS said . and if this is indeed a GRID deployment I would advise you to get professional service from SAS PSD team in your region. As SAS GRID deployment is not as simple as SAS 9.4 Platform, it has specials prerequisites, especially storage network file system requirements.     When I do deployments with PAM, the sas installer, sassrv and sasdemo are all already created at AD/LDAP level and can login at OS level and have home directories created. You can of course configure it to auto-create home directories for users on first login.   But I see you mentioned that sas installer account is created at OS level and not in AD/LDAP and that sassrv and sasdemo do not exist yet.   In order to understand if the issue is with PAM configuration or not, I would then do the deployment without PAM. so create sassrv and sasdemo accounts at OS level same as sas installer and do a deployment test, if it went successful then your challenge is with PAM configuration.   ... View more

Can you confirm that the SAS installer account, sassrv, and sasdemo are not OS local host accounts and are LDAP/AD accounts? Check the volume where you are deploying SAS (ex: /sas ) if having the nosuid and/or no_root_squash attributes set.  These attributes should not be set on SAS partition. Also what is the output of this command: <SASHome>/SASFoundation/9.4/utilities/bin/elsconf -v ... View more

Hi,   Can you confirm that you have run/executed the setuid.sh script, <SASHome>/SASFoundation/9.4/utilities/bin/setuid.sh, as root first, before configuration step?   Did you edited the file /<SASHome>/SASFoundation/9.4/utilities/bin/sasauth.conf for PAM authentication? The sasauth.conf file ships with the default value of methods=pw, for local host authentication only. I believe in your case it needs to be set to method=pam.       ... View more

Sorry I keep forgetting important points. but did you ran SAS 9 System Evaluation tool before starting your UIP? https://go.documentation.sas.com/doc/en/bicdc/9.4/contentassessment/n0b6u5fv19rtogn1322l2m4crxle.htm   You need first to run SAS9 System Evaluation first, then open a case with SAS TS to evaluate the output and give you feedback. ... View more

I forgot to mention that when I upgraded from M6 to M8, UIP did not upgrade SAS Internal database (PostgreSQL) and discovered that SAS PostgreSQL is still the old version. So please check SAS online documentation to verify your Postgresql version and on how to upgrade it. ... View more

I had multi-machine deployment and yes I did follow  knowledge base number KB0036368. I have also checked my screenshots and I confirm that I selected default option in SAS Wizard.   Also during my UIP process I used to exist second phase of the Wizard when it asks to select SASCONFIG for update and run SDM manually instead, SAS Deployment Manager, and choose Update Existing Configuration for two reasons:   1. the machines were using alias names and SAS Wizard does not pass alias names to SDM in the second step when it launch SDM automatically for you to update SASCOFIG so I had problems in that 2. the Wizard consumes lots of memory and tmp space so not to face a crash I stop the Wizard on SASCONFIG update phase, then I run SDM manually instead to update SASCONFIG.   Basically UIP process will do two thing when you run it: 1. Update SASHOME 2. Then it asks you to confirm SASCONFIG path to launch SDM automatically to update SASCONFIG   In the second step I exit the Wizard then I run SDM manually and select "Update Existing Configuration". On Mid-tier when I ran SDM manually I also used the javaoptions parameter to increase SDM memory size from 2GB to 4GB because it failed on first run (mid-tier SASCONFIG update consumed SDM default allocated memory of 2GB):   /opt/sas/sashome/SASDeploymentManager/9.4/sasdm.sh -javaoptions "-Xmx4096M"   A) Make sure that /tmp has at least 10GB free, preferred 20GB especially for Mid-Tier. B) Make sure that you have enough free memory - I first stopped SAS, rebooted Linux and then started SAS to free memory buffer/cache C) Make sure disk space is about 1.5 of SAS size - i.e: if SAS is installed in /sas directory and SASHOME and SASCONFIG are consuming 20GB, then you would need at least 30GB (20x1.5) of available disk space inside /sas directory ... View more

Thanks for the output, strange issue.   Have you checked if SELinux is enabled and in enforcing mode? Have you completed all SAS prerequisites for your SAS products and validate them?   To check if SELinux is enabled i.e enforcing, type sestatus, the output should not contain the keyword enforcing. SELinux should be in disabled or permissive mode only. IF you found SELinux is enabled and in enforcing mode,  then disable it first, after ttat stop SAS Wizard and run it back again.    Also do type "df -h" and see if /tmp has enough free space and no partition is full/almost full. ... View more

Hi,   I have also recently did UIP to M8 and did the steps in the SAS note.   As JuanS_OCS mentioned "hances are high that this configuration is just the one that comes by default in the prompt" and I did that too back then, I just moved with the default and didn't give it much of a thought and the UIP worked with no problems.   I hope you had a full environment backup (disk-cloning or image-cloning of the machines). because you do not know what you will face of challenges.   Regards, Ahmad ... View more

thank you for the screenshot.   using sas installer account, open SSH session to the machine and type:   which python python --version python -V   do you get any output? ... View more

Have you tried also to use full python path in SAS wizard dialog box: /usr/bin/python? ... View more

Hello,   A) Was it working before IRStudio? B) What has changed from last time it was running? C) Have you maybe updated Python version from 2.7 to 3.6? D) If IRStudio was installed with 2.x and you have updated to 3.x, it will not work E) Have you maybe updated Python from 3.x to 3.x where now the Python symlink in /usr/bin has been removed or it is now broken. F) have you check /usr/bin/python if the symlink exists and to where it is pointing?   I cant recall the file name but inside IRStudio directory in SASCONFIG there is a configuration or maybe XML file that has python path and version. check this file and see python path and its version if it exists at OS level.   Regards, Ahmad ... View more

I could see that your python symbolic link is pointing to /etc/alternatives/unversiond-python, I am not sure what this mean and its effect but have you tried to remove this symlink, create one for the python3.6 and then use the full path in SAS Wizard ex: /usr/bin/python ?   try below commands as root user: cd /usr/bin/ unlink python ln -s /usr/libexec/platform-python3.6 /usr/bin/python   then in SAS Wizard give it full path: /usr/bin/python and press Next.   hope that will help. ... View more

Is the services up? The error message is complaining that there is no service running on the specified machine on that port!. Is this deployment single machine or multi? Is it on Linux or Windows? Have you verified the services using SASMC? Have you checked the services if they are up? ex: using sas.servers script status on Linux   Regards, Ahmad ... View more

Dear @EdoardoRiva ,   Many thanks for this amazing article, you made a complex topic simple and easy. The images were done well and made me understand the concept easily.   I have one question which is a bit unusual but one of our customers don't want to use HTTPS between his reverse proxy and SAS Viya. he even said don't use SSL/TLS in your deployment we will do SSL handling and SSL offloading on our reverse proxy.  So basically in his infrastructure all vendor's applications sets behind his reverse proxy without SSL/TLS and he handles encryption and security at his entry point.   So end users will talk to their company's reverse proxy using HTTPS and then an SSL offloading happens at the reverse proxy, and a clear HTTP communication happens between reverse proxy and any backend application, like SAS Viya in this case.   But the online documentation has below requirement: - The external reverse proxy must use HTTPS    Not sure if this requirement is mandatory in case we are integrated with the Apache HTTP Server on port 443 or this requirement is mandatory whether integrating with port 80, 443 or any other port.   Do you have an idea if this kind of integration can happen between client's reverse proxy and Apache HTTP Server on port 80 using HTTP only?  And if it is possible what changes do we have to do at the Apache level and SAS Viya level, since the official publish changes talks about 443 and HTTPS.   Thank you, Ahmad ... View more