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: 

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).

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
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.

---

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at

http://documentation.sas.com/?softwareId=administration&softwareVersion=3.5&softwareContextId=softwareUpdates

---

A fix for this issue for Base SAS 9.4_M7 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/I9R.html#68611

---

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-09-26 09:10:24
Date Created:	2021-11-16 16:23:57