You may encounter the "The compute server session is in a failed state" message in the either of the following circumstances:

• You attempt to launch a SAS Studio V session. In this scenario, the message is displayed in the user interface.
• SAS Studio V fails with no error message. In this scenario, the message is displayed in the SAS Studio V logs.

There are a few possible causes for this issue:

• Changes were made directly to server configuration files. 
• Changes were made to the vars.yml file (located here: /sas/install/sas_viya_playbook/vars.yml)​​​, which affected the server configuration files, and then the playbook was ran.
• The SASWORK location is out of space.

For example, in the vars.yml file, there is a section near the end that allows you to add more keys/options to the server configuration files:

If you set an incorrect value here, it gets written to the following server configuration folders (should they exist): connect, workspace, compute, and batch. 

To work around this issue, you must find the incorrect values that were written to each of the server configuration files (sasenv_deployment, sasv9_deployment.cfg, autoexec_deployment.sas) and correct them. Here are the locations of the various server configuration files:

• compute server: /opt/sas/viya/config/etc/compsrv/default/*.cfg
• workspace server: /opt/sas/viya/config/etc/workspaceserver/default/*.cfg
• connect server: /opt/sas/viya/config/etc/connectserver/default/*.cfg
• batch server: /opt/sas/viya/config/etc/batchserver/default/*.cfg

If you made this mistake in the vars.yml file, you also must correct it to prevent the incorrect options from being written to these files again if the playbook is rerun. 

Operating System and Release Information