SUPPORT / SAMPLES & SAS NOTES
 

Support

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

DetailsHotfixAboutRate It

In a SAS Viya 2020 environment, you can launch the SAS/CONNECT server 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. This method is known as a locally launched SAS/CONNECT server.
  • 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.

Beginning in stable 2024.03 and Long-Term Support, the locally launched SAS/CONNECT server was deprecated. 

Beginning in stable 2024.09, the ability to locally spawn a SAS/CONNECT server inside the SAS/CONNECT spawner pod has been removed.

SAS® 9.4M6 (TS1M6) and earlier clients can connect to only a locally launched SAS/CONNECT server. These clients will not be able to connect to a 2024.03 and later SAS/CONNECT spawner. As a result, you should migrate to SAS® 9.4M7 (TS1M7) or later.

When a SAS 9.4M7 or SAS® Viya® 3.5 client tries to connect to the SAS/CONNECT spawner in SAS Viya 2020 and later releases with the -nolocallaunch option, the connection might fail with the following message: 

Error: Cannot start remote process

To allow the SAS 9.4M7 or SAS Viya 3.5 client to handle a new communication flow with the SAS Viya 2020 and later SAS/CONNECT spawner using the -nolocallaunch option, a hot fix for the SAS 9.4M7 and SAS Viya 3.5 client is required. 

Click the Hot Fix tab in this note to access the hot fix for this issue.

NOTE:

  • SAS/CONNECT servers launching in a new pod has been the default behavior for SIGNONs to the SAS/CONNECT spawner (SAS Viya) since 2021 (-nolocallaunch).
  • The error below can be caused by other issues (that is, anything that would cause the SAS/CONNECT server to start).
Error: Cannot start remote process


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS/CONNECTz/OS9.4_M79.4 TS1M7
z/OS 64-bit9.4_M79.4 TS1M7
Microsoft® Windows® for x649.4_M79.4 TS1M7
Microsoft Windows 8 Enterprise 32-bit9.4_M79.4 TS1M7
Microsoft Windows 8 Enterprise x649.4_M79.4 TS1M7
Microsoft Windows 8 Pro 32-bit9.4_M79.4 TS1M7
Microsoft Windows 8 Pro x649.4_M79.4 TS1M7
Microsoft Windows 8.1 Enterprise 32-bit9.4_M79.4 TS1M7
Microsoft Windows 8.1 Enterprise x649.4_M79.4 TS1M7
Microsoft Windows 8.1 Pro 32-bit9.4_M79.4 TS1M7
Microsoft Windows 8.1 Pro x649.4_M79.4 TS1M7
Microsoft Windows 109.4_M79.4 TS1M7
Microsoft Windows Server 20089.4_M79.4 TS1M7
Microsoft Windows Server 2008 R29.4_M79.4 TS1M7
Microsoft Windows Server 2008 for x649.4_M79.4 TS1M7
Microsoft Windows Server 2012 Datacenter9.4_M79.4 TS1M7
Microsoft Windows Server 2012 R2 Datacenter9.4_M79.4 TS1M7
Microsoft Windows Server 2012 R2 Std9.4_M79.4 TS1M7
Microsoft Windows Server 2012 Std9.4_M79.4 TS1M7
Microsoft Windows Server 20169.4_M79.4 TS1M7
Microsoft Windows Server 20199.4_M79.4 TS1M7
Windows 7 Enterprise 32 bit9.4_M79.4 TS1M7
Windows 7 Enterprise x649.4_M79.4 TS1M7
Windows 7 Home Premium 32 bit9.4_M79.4 TS1M7
Windows 7 Home Premium x649.4_M79.4 TS1M7
Windows 7 Professional 32 bit9.4_M79.4 TS1M7
Windows 7 Professional x649.4_M79.4 TS1M7
Windows 7 Ultimate 32 bit9.4_M79.4 TS1M7
Windows 7 Ultimate x649.4_M79.4 TS1M7
64-bit Enabled AIX9.4_M79.4 TS1M7
64-bit Enabled Solaris9.4_M79.4 TS1M7
HP-UX IPF9.4_M79.4 TS1M7
Linux for x649.4_M79.4 TS1M7
Solaris for x649.4_M79.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.