Sign-on connections to the SAS/CONNECT spawner might fail sporadically if the SAS/CONNECT^® server does not start within 60 seconds. As a result, errors similar to the following occur in the SAS/CONNECT spawner log:

Note that the connection time-out is exactly 60 seconds. This value cannot be changed. This issue is usually caused by a high load on the server.

If this problem occurs, you should try and determine why the server is taking so long to launch a SAS/CONNECT session. Depending on how often this problem occurs, a programming solution might be considered such as a sign-on macro that will retry should the SIGNON command fail. See the attached code on the Full Code tab for a simple example.

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 TS1M8
		z/OS 64-bit	9.4_M7		9.4 TS1M8
		Microsoft® Windows® for x64	9.4_M7		9.4 TS1M8
		Microsoft Windows 8 Enterprise 32-bit	9.4_M7		9.4 TS1M8
		Microsoft Windows 8 Enterprise x64	9.4_M7		9.4 TS1M8
		Microsoft Windows 8 Pro 32-bit	9.4_M7		9.4 TS1M8
		Microsoft Windows 8 Pro x64	9.4_M7		9.4 TS1M8
		Microsoft Windows 8.1 Enterprise 32-bit	9.4_M7		9.4 TS1M8
		Microsoft Windows 8.1 Enterprise x64	9.4_M7		9.4 TS1M8
		Microsoft Windows 8.1 Pro 32-bit	9.4_M7		9.4 TS1M8
		Microsoft Windows 8.1 Pro x64	9.4_M7		9.4 TS1M8
		Microsoft Windows 10	9.4_M7		9.4 TS1M8
		Microsoft Windows 11	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2008	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2008 R2	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2008 for x64	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2012 Datacenter	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2012 R2 Datacenter	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2012 R2 Std	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2012 Std	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2016	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2019	9.4_M7		9.4 TS1M8
		Microsoft Windows Server 2022	9.4_M7		9.4 TS1M8
		Windows 7 Enterprise 32 bit	9.4_M7		9.4 TS1M8
		Windows 7 Enterprise x64	9.4_M7		9.4 TS1M8
		Windows 7 Home Premium 32 bit	9.4_M7		9.4 TS1M8
		Windows 7 Home Premium x64	9.4_M7		9.4 TS1M8
		Windows 7 Professional 32 bit	9.4_M7		9.4 TS1M8
		Windows 7 Professional x64	9.4_M7		9.4 TS1M8
		Windows 7 Ultimate 32 bit	9.4_M7		9.4 TS1M8
		Windows 7 Ultimate x64	9.4_M7		9.4 TS1M8
		64-bit Enabled AIX	9.4_M7		9.4 TS1M8
		64-bit Enabled Solaris	9.4_M7		9.4 TS1M8
		HP-UX IPF	9.4_M7		9.4 TS1M8
		Linux for x64	9.4_M7		9.4 TS1M8
		Solaris for x64	9.4_M7		9.4 TS1M8

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

Here is a simple macro to check the signon attempt and retry if it fails.

---

%macro signon_retry(session, retries, user, passwd);
    %local attempt rc;

    %do attempt = 1 %to &retries;
        %put Attempting to sign on to &session. Attempt &attempt of &retries;
        signon session user=&user password=&passwd CMACVAR=signon_rc; 

        /* Check if signon was successful */
        %if "&signon_rc" ne "0" %then %do;
            %put Signon to &session failed. Retrying...;
        %end;
        %else %do;
            %put Signon to &session successful.;
            %return; /* Exit macro if signon is successful */
        %end;

        %if &attempt = &retries %then %do;
            %put Maximum number of retries reached. Unable to signon to &hostname.;
            %return;
        %end;
    %end;
%mend;

/* To call the macro, the session parameter is the host and port of the spawner, 
retries is the number of signon attempts with user and password the user credentials. For example: */

%signon_retry(session=sas94server 7551, retries=3, user=sasdemo, passwd=mypassword);

Type:	Problem Note
Priority:	medium

Date Modified:	2024-05-17 12:44:59
Date Created:	2024-05-10 06:53:08