The SAS Stored Process Server did not support NAT (Network Address Translation) prior to SAS 9.1.3 SP3. For example, suppose a machine called "aa.bb.com" is known externally as 192.111.111.11 (and only by this IP address). NAT, however, translates this IP address to an internal address of 213.222.22.22 (and "aa.bb.com" is known internally only by this IP address). Then, the SAS Stored Process Server could be configured to support both an external client and an internal client.

If you encounter this problem, you might receive an error message that is similar to the following when you run a "Test Connection" test for the SAS Stored Process Server from the SAS^® Management Console:

    sam.S249.ex.msg: A connection to server host could not be
    established on port 8621. Either there is no server listening
    for connections or the server is too busy to access any new
    connections.

Beginning with SAS 9.1.3 SP3, the Object Spawner has a new option called "lbUseHostName". This option causes the host name (rather than the IP address) to be used for Load Balancing (for redirection to the Stored Process Servers). In addition to specifying the –lbUseHostName option for the Object Spawner startup, the server host name (not the IP address) should be specified for the server definitions in SAS Management Console.

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

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :