SUPPORT / SAMPLES & SAS NOTES
 

Support

Usage Note 18503: You cannot connect to the SAS® 9.1.3 or SAS® 9.2 Stored Process Servers under UNIX from client applications under Windows when NAT is used

DetailsAboutRate It

You might receive an error message similar to the following when attempting to test the connection to a SAS 9.1.3 or SAS 9.2 Stored Process Server under UNIX using SAS® Management Console running on a Windows platform:

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

Other symptoms of this issue might include the following:

  • The same Stored Process Server test connection is successful from SAS Management Console on the UNIX host.
  • Stored Processes can be executed from a web client (such as Portal, SAS® Web Report Studio, STP Web Application) but not from a Windows client such as SAS® Enterprise Guide®, SAS® Add-In for Microsoft Office, or SAS Management Console.

This problem occurs when the network uses Network Address Translation (NAT). For more information about running the Stored Process Server on a network that uses NAT, see SAS Note 15049.

If NAT is being used and the connection to the Stored Process Server running on UNIX fails only from Windows clients, then the problem can be corrected by specifying the -lbUseHostName option when starting the Object Spawner process on UNIX (as outlined in SAS Note 15049). The problem occurs when the IP address that appears to the Windows client is not the actual IP address on the server due to NAT translation. By using -lbUseHostName in the SAS® Object Spawner invocation, the actual host name is used instead of the host's IP address. Therefore, the Windows client can find the server host.

The -lbUseHostName option is specified in the ObjectSpawner.sh script, as shown here:

nohup $CMD -sasSpawnerCn "$SPWNNAME" -lbUseHostName -omrconfigfile $XMLCFG > $DIR/logs /objspawn_console.log 2>&1 &

You must restart the Object Spawner after making any changes to the ObjectSpawner.sh script. Here is documentation about Object Spawner invocation options.

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.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS Integration TechnologiesMicrosoft Windows XP Professional9.1 TS1M3
Microsoft Windows XP 64-bit Edition9.1 TS1M3
Microsoft Windows NT Workstation9.1 TS1M3
Microsoft® Windows® for 64-Bit Itanium-based Systems9.1 TS1M3
Microsoft Windows Server 2003 Standard Edition9.1 TS1M3
Microsoft Windows 2000 Server9.1 TS1M3
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M3
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M3
Microsoft Windows 2000 Datacenter Server9.1 TS1M3
Microsoft Windows 2000 Professional9.1 TS1M3
64-bit Enabled Solaris9.1 TS1M3
Microsoft Windows 2000 Advanced Server9.1 TS1M3
z/OS9.1 TS1M3
Linux9.1 TS1M3
64-bit Enabled HP-UX9.1 TS1M3
Linux on Itanium9.1 TS1M3
HP-UX IPF9.1 TS1M3
OpenVMS Alpha9.1 TS1M3
64-bit Enabled AIX9.1 TS1M3
Tru64 UNIX9.1 TS1M3
z/OS 64-bit9.2 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.2 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.2 TS1M0
Microsoft® Windows® for x649.2 TS1M0
Windows Vista9.2 TS1M0
Windows Vista for x649.2 TS1M0
Linux for x649.2 TS1M0
OpenVMS on HP Integrity9.2 TS1M0
Solaris for x649.2 TS1M0
* 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.