SAS install instructions


In order to enable SAS notebooks for an organization (or individual account), you must provide your license information. Because of how SAS handles cloud deployments, the steps to enable SAS are a bit more complicated than for Stata. Specifically, you'll need to complete the following steps:

For the easiest install experience, we recommend using a clean linux VM on a cloud provider in order to perform installation. Make sure the VM has at least 50GB of disk space to properly install SAS and create the final .tar file. We have encountered some issues when performing the installation within a docker container on M-series (ARM) Macs. If you only have access to an M-series Mac, use docker buildx instead. E.g.:

docker buildx build --platform linux/amd64 -t <IMAGE-NAME>:<TAG>


  1. IMPORTANT: Make sure all system requirements for SAS 9.4 are installed on your system (e.g., numactl). If these dependencies aren't all installed, you will encounter errors later on that will require you to restart install process (and these errors can be a bit cryptic). Consult page 3 of the SAS 9.4 requirements document for full details.

  2. Run SAS Deployment Wizard to install SAS Studio on a supported Linux 64-bit operating system. During the installation, change the default location for the SAS Studio installation to /usr/local/SASHome.

    • If you are provided SAS as a zip file called ​​, you would first unzip the file in your home directory: unzip

      1. Change permissions on the new folder so you can complete the setup: chmod -R 0775 ./SAS_94_TS1M7/

      2. Create the directory where SAS will be installed: mkdir /usr/local/SASHome

      3. You will also want to change ownership of the location where you will install SAS (i.e. /usr/local ): sudo chown -R $(whoami) /usr/local/

      4. Change directory to the unzipped folder: cd SAS_94_TS1M7

    • If you are provided with the SAS Download Manager as a source file instead (e.g., esdclient__94604__lax__xx__web__1 - 78MB), you would:

      • Make the file executable, extract it to a folder, and run to set things like language, order options, software depot options, etc. in order to create the depot and download the software:

        $ chmod u+x esdclient__94604__lax__xx__web__1
        $ mkdir sasInstall
        $ ./esdclient__94604__lax__xx__web__1 --target ./sasInstall
        $ cd sasInstall
        $ ./ -console
  3. While still in the top level directory of the SAS installation package, you can now run the SAS Deployment wizard in the terminal using the -console flag: ./ -console. You should now see the Deployment wizard start up.

  1. For most configuration steps, you should be able to use the default selection. EXCEPT for the following:

    • Home location: set to /usr/local/SASHome (if not the default )

  • Add SAS Studio to the list of products to Install SAS Foundation and related software

  • Make sure you set the SAS Studio configuration home as: /usr/local/SASHome/sas/studioconfig (if not, it will install by default in the root directory (i.e. /sas/studioconfig), outside of the location where you are installing SAS. This will render the installation unusable when it is time to tar it and load into a Docker image according to the steps below ).

  1. Before the actual installation process starts, you will see a list of all installation steps that will be completed during the set up. After these finish, you will want to make sure that all of these steps were completed Successfully in the installation report - the tail of which is copied below.

  1. If you had any steps marked with E (Completed with errors), you may need to check the log files at /usr/local/SASHome/InstallMisc/InstallLogs​​/ - you can refer to this SAS Resource for troubleshooting installation issues:

  2. There will likely be a lot of log files. Likely of interest are the IT_<date-time>.log and the IT_<date-time>_fileslist.log . For example, if the numactl dependency is missing, you'll see a log similar to

    2023-12-05 02:01:54   InstallationTask -  Cannot dlopen [] : [ cannot open shared object file: No such file or directory

    At this point, you'll need to uninstall SAS and start over again.

  3. If there are errors on installation, you can correct the problem noted in the logs and re-run the SAS Deployment Wizard with ~/SAS_94_TS1M7/

  4. Run /usr/local/SASHome/SASFoundation/9.4/utilities/bin/ as root

  5. Once all steps complete successfully, you can make sure SASStudio works before packaging it up by running the following: /usr/local/SASHome/sas/studioconfig/ start. If you see that the Spawner and the SAS Web Application Server have both started and have their own process ids, you should be ready to move forward. For good measure, make sure to stop these processes before creating the TAR file: /usr/local/SASHome/sas/studioconfig/ stop

    1. Note: if you are getting errors at this stage or the Spawner and Application Server are not starting as expected, you should make sure that you have installed all the Linux packages listed in the SAS documentation here in the section titled Docker Checklist:

  6. For more information on starting and stopping the Spawner and Web Application Server for SAS Studio, please refer to:

  7. For details and troubleshooting about how to install SAS Studio, refer to the installation and configuration instructions provided by the product.

    1. In general, it might help to refer to this SAS Resource to troubleshoot installation problems:

  8. Create a TAR file that includes the SASHome directory: tar -cvf SASHome.tar /usr/local/SASHome

Once this tar file has been created, please reach out to your Redivis contact, or, to share the file so that we can enable SAS for your account.

To uninstall SAS, run:

$ cd /usr/local/SASHome/SASDeploymentManager/9.4/

$ ./ -console

Last updated