Issue in deploying SAS9.4M8 - The directory does not contain the requested components

[Amitkum2]

Hi,

I am deploying SAS9.4M8 on RHEL8.5 servers. While deploying application server, i was getting SAS configuration of python prompt. When i proceed further it gives "The directory does not contain the requested components"

I have python 2.7 as well as 3.6 installed. I tried giving different paths but everytime i am getting the same msg.

[sys-halt]

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.

[Amitkum2]

Hi @sys-halt 

Thanks for your response !!

I tried creating new symlink for python but still getting the same error.

[sys-halt]

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

[Amitkum2]

Yes,

[sys-halt]

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?

[Amitkum2]

PFB the output

[sys-halt]

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.

[Amitkum2 · Accepted solution]

Hello @sys-halt ,

Thanks for providing your input on the issue !!

After making the selinux permissive, i am able to cross the step.

Thanks for quick help !