Problem Note 63260: You see "The compute server session is in a failed state" when you try to log on to or are using SAS® Studio
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:
# Updates the workspaceserver autoexec_deployment.sas
#WORKSPACESERVER_CONFIGURATION:
#1: '/* Comment about key */'
#2: key=value;
# Creates a workspaceserver sasenv_deployment file
#FOUNDATION_CONFIGURATION:
#1: '# Comment about KEY'
#2: KEY=value
# Creates a workspaceserver sasv9_deployment.cfg file
#SASV9_CONFIGURATION:
#1: '/* Comment about OPTION */'
#2: 'OPTION value'
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
| SAS System | SAS Viya | Microsoft® Windows® for x64 | | |
| Microsoft Windows 8 Enterprise 32-bit | | |
| Microsoft Windows 8 Enterprise x64 | | |
| Microsoft Windows 8 Pro 32-bit | | |
| Microsoft Windows 8 Pro x64 | | |
| Microsoft Windows 8.1 Enterprise 32-bit | | |
| Microsoft Windows 8.1 Enterprise x64 | | |
| Microsoft Windows 8.1 Pro 32-bit | | |
| Microsoft Windows 8.1 Pro x64 | | |
| Microsoft Windows 10 | | |
| Microsoft Windows 95/98 | | |
| Microsoft Windows 2000 Advanced Server | | |
| Microsoft Windows 2000 Datacenter Server | | |
| Microsoft Windows 2000 Server | | |
| Microsoft Windows 2000 Professional | | |
| Microsoft Windows NT Workstation | | |
| Microsoft Windows Server 2003 Datacenter Edition | | |
| Microsoft Windows Server 2003 Enterprise Edition | | |
| Microsoft Windows Server 2003 Standard Edition | | |
| Microsoft Windows Server 2003 for x64 | | |
| Microsoft Windows Server 2008 | | |
| Microsoft Windows Server 2008 R2 | | |
| Microsoft Windows Server 2008 for x64 | | |
| Microsoft Windows Server 2012 Datacenter | | |
| Microsoft Windows Server 2012 R2 Datacenter | | |
| Microsoft Windows Server 2012 R2 Std | | |
| Microsoft Windows Server 2012 Std | | |
| Microsoft Windows Server 2016 | | |
| Microsoft Windows XP Professional | | |
| Windows 7 Enterprise 32 bit | | |
| Windows 7 Enterprise x64 | | |
| Windows 7 Home Premium 32 bit | | |
| Windows 7 Home Premium x64 | | |
| Windows 7 Professional 32 bit | | |
| Windows 7 Professional x64 | | |
| Windows 7 Ultimate 32 bit | | |
| Windows 7 Ultimate x64 | | |
| Windows Millennium Edition (Me) | | |
| Windows Vista | | |
| Windows Vista for x64 | | |
| Linux for x64 | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
You might see this message in the SAS® Studio V user interface or in the SAS Studio V logs: "The compute server session is in a failed state."
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2018-12-03 15:12:28 |
| Date Created: | 2018-11-26 14:56:31 |