Usage Note 68611: A SAS/CONNECT® client signon on SAS® 9.x or SAS® Viya® 3.x to a SAS/CONNECT spawner for SAS® Viya® 2020 and later fails with an error.
In a SAS Viya 2020 environment, the SAS/CONNECT server can be launched in the following two ways:
- in the same pod as the SAS/CONNECT spawner (this configuration uses security settings on the container for the SAS/CONNECT spawner)
- in a separate pod from the SAS/CONNECT spawner (in this scenario, the SAS/CONNECT spawner is launched with the -nolocallaunch parameter; this configuration ensures better management of resource utilization within the Kubernetes cluster, ensures user-level process isolation, and meets compliance requirements for container security)
When a SAS®9 client attempts to connect to the SAS/CONNECT spawner in SAS Viya 2020 and later releases with the -nolocallaunch option (which launches the SAS/CONNECT server in a separate pod from the SAS/CONNECT spawner), the connection fails with the following message:
Error: Cannot start remote process
For a SAS® 9.4M7 (TS1M7) or SAS® Viya® 3.5 client to connect successfully to the SAS/CONNECT spawner started with the -nolocallaunch option, the SAS/CONNECT client for SAS 9.4M7 must handle a new communication flow.
To enable this new communication flow, a hot fix for SAS 9.4M7 and SAS Viya 3.5 is required.
Click the Hot Fix tab in this note to access the hot fix for this issue.
In order for a SAS/CONNECT client using other SAS9 releases to successfully connect to a SAS/CONNECT spawner using -nolocallaunch, you must do one of the following:
- Change the security settings of the container for the SAS/CONNECT spawner back to a more unsecured state.
- Start the SAS/CONNECT spawner without -nolocallaunch. The SAS/CONNECT server then launches in the same pod as the SAS/CONNECT spawner.
NOTE:
- SAS/CONNECT servers launching in a new pod has been the default behavior for SIGNONs to the CONNECT Spawner (SAS Viya) since 2021 (-nolocallaunch).
- Beginning in 2024.09, the ability to use locally launched SAS/CONNECT servers will be deprecated. SAS clients at SAS 9.4M6 and earlier will not be able to reach launched SAS/CONNECT Server pods.
Operating System and Release Information
SAS System | SAS/CONNECT | z/OS | 9.4_M7 | | 9.4 TS1M7 | |
z/OS 64-bit | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft® Windows® for x64 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 8 Enterprise 32-bit | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 8 Enterprise x64 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 8 Pro 32-bit | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 8 Pro x64 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 8.1 Enterprise x64 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 8.1 Pro 32-bit | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 8.1 Pro x64 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows 10 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2008 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2008 R2 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2008 for x64 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2012 Datacenter | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2012 R2 Std | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2012 Std | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2016 | 9.4_M7 | | 9.4 TS1M7 | |
Microsoft Windows Server 2019 | 9.4_M7 | | 9.4 TS1M7 | |
Windows 7 Enterprise 32 bit | 9.4_M7 | | 9.4 TS1M7 | |
Windows 7 Enterprise x64 | 9.4_M7 | | 9.4 TS1M7 | |
Windows 7 Home Premium 32 bit | 9.4_M7 | | 9.4 TS1M7 | |
Windows 7 Home Premium x64 | 9.4_M7 | | 9.4 TS1M7 | |
Windows 7 Professional 32 bit | 9.4_M7 | | 9.4 TS1M7 | |
Windows 7 Professional x64 | 9.4_M7 | | 9.4 TS1M7 | |
Windows 7 Ultimate 32 bit | 9.4_M7 | | 9.4 TS1M7 | |
Windows 7 Ultimate x64 | 9.4_M7 | | 9.4 TS1M7 | |
64-bit Enabled AIX | 9.4_M7 | | 9.4 TS1M7 | |
64-bit Enabled Solaris | 9.4_M7 | | 9.4 TS1M7 | |
HP-UX IPF | 9.4_M7 | | 9.4 TS1M7 | |
Linux for x64 | 9.4_M7 | | 9.4 TS1M7 | |
Solaris for x64 | 9.4_M7 | | 9.4 TS1M7 | |
*
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.
In this failing scenario, the SAS/CONNECT spawner in SAS Viya is started with the -nolocallaunch option and the client is SAS®9.
Type: | Usage Note |
Priority: | high |
Date Modified: | 2024-03-15 16:26:15 |
Date Created: | 2021-11-16 16:23:57 |