Usage Note 35532: ERROR: "Bridge protocol engine socket access method failed to bind listen socket, error 10048 (The specified address is already in use.)"
The following error might occur in the SAS® Stored Process Server log file:
ERROR: Bridge protocol engine socket access method failed to bind listen socket,
error 10048 (The specified address is already in use.).
Each multibridge connection of a SAS Stored Process Server is defined to start on a specific port, and this error indicates that the port for this particular multibridge connection is already being used by another process. Unfortunately the port number is not included in the error message.
If this is a new installation, then it might be necessary to select different ports for the stored process server bridge or multibridge connections. The default bridge port is 8601 and the default multibridge ports for a load–balanced stored process server are 8611, 8621 and 8631. You should check with your systems administrator to determine if the ports specified in your configuration are available on the stored process server host machine. The ports for the stored process server can be viewed and changed from SAS® Management Console using the Server Manager plug-in by doing the following:
- Expand the Logical Stored Process Server and highlight the Stored Process Server object. The Connection Name, Host name, Port and Protocol will display in the right–hand pane of SAS Management Console.
- If you need to change a port number, right -click the Connection Name object you want to change and open the Properties.
- Select the Options tab and change the port.
- Click OK to close the Properties and save the change.
- It will be necessary to restart the Object Spawner after making changes to the Stored Process Server definition in SAS Management Console.
If the stored process servers were functioning properly prior to receiving this error, it is likely that there are one or more stored process servers still running but they have become unresponsive and are orphaned processes. To restore the servers, follow step 3 "Evaluate SAS Processes After Terminating the Object Spawner" and step 5 "Stop Existing Stored Process Servers and Restart the Object Spawner" in SAS Note 30952 "Tips for addressing unresponsive SAS® Stored Process Servers, Part 1".
Operating System and Release Information
| SAS System | SAS Integration Technologies | z/OS | | |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | | |
| Microsoft Windows XP 64-bit Edition | | |
| Microsoft® Windows® for x64 | | |
| Microsoft Windows 95/98 | | |
| Microsoft Windows 2000 Advanced Server | | |
| Microsoft Windows 2000 Datacenter Server | | |
| Microsoft Windows 2000 Server | | |
| Microsoft Windows 2000 Professional | | |
| Microsoft Windows NT Workstation | | |
| Microsoft Windows Server 2003 Datacenter Edition | | |
| Microsoft Windows Server 2003 Enterprise Edition | | |
| Microsoft Windows Server 2003 Standard Edition | | |
| Microsoft Windows Server 2008 | | |
| Microsoft Windows XP Professional | | |
| Windows Millennium Edition (Me) | | |
| Windows Vista | | |
| 64-bit Enabled AIX | | |
| 64-bit Enabled HP-UX | | |
| 64-bit Enabled Solaris | | |
| AIX | | |
| HP-UX | | |
| HP-UX IPF | | |
| Linux | | |
| Linux for x64 | | |
| Linux on Itanium | | |
| OpenVMS Alpha | | |
| OpenVMS on HP Integrity | | |
| Solaris | | |
| Solaris for x64 | | |
| Tru64 UNIX | | |
*
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.
| Type: | Usage Note |
| Priority: | |
| Topic: | System Administration ==> Servers ==> Integration Technologies
|
| Date Modified: | 2009-07-30 16:41:49 |
| Date Created: | 2009-04-13 09:17:13 |