Usage Note 14819: "Bridge protocol engine socket access method was unable to connect an
outcall socket to name_or_ip:port" error message when performing Update
Table Metadata within SAS ETL Studio software
You may receive one of the following errors in the SAS log when
attempting to execute an "Update Table Metadata" from within SAS ETL
Studio:
ERROR: Bridge protocol engine socket access method was unable to
connect an outcall socket to machine_or_IP:port, error = 0 (An
unexpected error has occurred.).
ERROR: Bridge protocol engine socket access method was unable to
connect an outcall socket to machine_or_IP:port, error = 145 (The
connection has timed out.).
These errors occur when the update process, executing on the workspace
server, cannot successfully connect back to the metadata server.
The connection information used by the update process is obtained from
the METASERVER and METAPORT system options. These options get set
automatically in the submitted code by SAS ETL Studio based on the
values of the Machine: and Port: fields found in the connection
information section of the metadata profile used during startup of SAS
ETL Studio.
Possible reasons why this may occur are as follows:
- An IP address, instead of a machine name, was specified for the
Machine: value, and this IP address is not valid from the workspace
server. This can occur if the metadata server and workspace server
are on different networks and use different sets of IP addresses
for machines.
- A machine name was specified for the Machine: value that the
workspace server cannot resolve. This can be caused by not specifying
the fully qualified server name, or by the machine name not being
in the host lookup table that is referenced by the workspace server.
Solution:
- Make sure the machine name or IP address specified in the metadata
profile can be resolved and/or accessed from the workspace server.
Operating System and Release Information
SAS System | SAS Data Integration Studio | Microsoft Windows NT Workstation | 3.2 | | 9.1 TS1M3 | |
Microsoft Windows XP Professional | 3.2 | | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Enterprise Edition | 3.2 | | 9.1 TS1M3 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 3.2 | | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Standard Edition | 3.2 | | 9.1 TS1M3 | |
Microsoft Windows 2000 Server | 3.2 | | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Datacenter Edition | 3.2 | | 9.1 TS1M3 | |
Microsoft Windows 2000 Professional | 3.2 | | 9.1 TS1M3 | |
Microsoft Windows 2000 Datacenter Server | 3.2 | | 9.1 TS1M3 | |
Microsoft Windows 2000 Advanced Server | 3.2 | | 9.1 TS1M3 | |
64-bit Enabled Solaris | 3.2 | | 9.1 TS1M3 | |
64-bit Enabled HP-UX | 3.2 | | 9.1 TS1M3 | |
Linux | 3.2 | | 9.1 TS1M3 | |
HP-UX IPF | 3.2 | | 9.1 TS1M3 | |
OpenVMS Alpha | 3.2 | | 9.1 TS1M3 | |
64-bit Enabled AIX | 3.2 | | 9.1 TS1M3 | |
Tru64 UNIX | 3.2 | | 9.1 TS1M3 | |
*
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.
Date Modified: | 2006-02-17 16:08:10 |
Date Created: | 2005-03-22 13:09:14 |