The SAS^® Stored Process Server may signal the object spawner that it is ready for the client connection before the listen port is available. If the client attempts to connect to the SAS Stored Process Server before the listen port is available, an error similar to the following will occur:

The application could not log on to the server "foo.unx.sas.com:8611". 
No server is available at that port on that machine.

This error usually occurs due to the port not being open on a firewall or a DNS resolution problem. It is extremely rare for this error to occur because the listen port was not available when the client tried to connect. Debug logging on the object spawner and SAS Stored Process Server is necessary to determine why this error occurred.

When debug logging is enabled, the time stamp in the SAS Stored Process Server log for activating the listen port will be later than the time stamp in the object spawner log for the redirect of the client into the SAS Stored Process Server.

The SAS Stored Process Server Log will contain:

 sassrv - Activated listen on IPv6 port 8611 (connection 1).

Redirecting peer [::ffff:10.11.14.215]:64352 to IP foo.unx.sas.com, port 8611

Operating System and Release Information

A fix for this issue for Base SAS 9.21_M3 is available at: