ISAS began installing SAS Enterprise Business Intelligence (EBI) 9.4 Maintenance Release 3 software on AIX 7.1 LPARs this summer. These were development environments which were single-machine deployments. The installation and configuration phases were straightforward, and when completed, the deployment was up and running and validated perfectly. I then shut down all of the SAS services using the sas.servers script which is created at the end of the configuration phase. I then used the script to start all of the services, and SAS reported everything was up and running, so I performed another round of validation. When I opened up a browser and supplied the URL of the Environment Manager, the browser reported that there was not an application running on that server and port. I stopped and started the SAS services many times with the sas.servers script to make sure the problem was consistently occurring, which it was.

I then opened up PuTTy and went straight to the <sasconfig>Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/bin/ script and executed a shutdown, only to be told that the Environment Manager server wasn’t running. So I then used the same script to start the server, and I went back to my browser and I was able to log into the application to validate.

Just out of curiosity, I contacted SAS Technical Support and asked them why this happened. The Tech Support Analyst told me that I was probably experiencing a known defect in the script on AIX. The problem is that if you issue the script from outside the <sasconfig>Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/bin directory, which is what is happening when we use the sas.servers script, then we will see a “../lib not found” error in the log.

To prevent this from happening, the script needs to be modified in two places, replacing the relative path to an absolute path to the lib directory. So to fix the problem, edit the <sasconfig>Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/bin/ script and change the following:


INPUT=`ls -m ../lib`
for i in $INPUT
   if [ -f "../lib/${i}" ]; then


INPUT=`ls –m <sasconfig>/Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/lib`
for i in $INPUT
   if [ -f "<sasconfig>/Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/lib/${i}" ]; then

where <sasconfig> is the fully qualified path to configuration directory.

With the absolute path provided, SAS knows where the appropriate binaries are located to start up the Environment Manager!

Oddly, this seems to be an AIX thing, because I have a few Red Hat Linux environments running SAS Visual Analytics and the Environment Manager, and never saw this issue.

Email this to someoneTweet about this on TwitterShare on LinkedIn0Pin on Pinterest0Share on Google+0Share on Facebook0Print this page