Problem Note 18417: Ignoring server due to machine name mismatch when starting the SAS Object Spawner on a machine with multiple network interface card
When installing the SAS Object Spawner on a machine with multiple Network Interface Cards (NIC), the Object Spawner might fail to start, and the following message displays in the Object Spawner log file:
Ignoring server xxxxxxxx.yyyyyyyy due to machine name mismatch.
Skipping server definition (xxxxxxxx.yyyyyyyy).
Defined server listen connection (4) on port 8571.
ERROR: Objspawn was unable to locate a server definition. Objspawn
is exiting.
The top of the SAS Object Spawner log will display the host name in which
the SAS Object Spawner is attempting to start. For example:
Objspawn version 3.0.0 is initializing.
Objspawn is executing on host machine1.mycompany.com (10.11.12.13).
Here are specific steps to use with a SAS® Enterprise Miner™ Personal Workstation or one machine install.
- Edit the ObjectSpawner.bat file
This file is located in "C:\SAS\EMiner\Lev1\SASMain\ObjectSpawner." Add the following options to the three lines that begin "start /b":
-dnsname 127.0.0.1 -dnsmatch 127.0.0.1
The options should be inserted into the lines just prior to "-OMRconfigfile".
- Uninstall/Install ObjectSpawner service
Open a DOS command window and change directories to:
"C:\SAS\EMiner\Lev1\SASMain\ObjectSpawner"
Enter these two commands:
objectspawner.bat -remove
objectspawner.bat -install
- Open Windows Services
Start SAS Lev1 OB - Eminer service and confirm that OB service starts successfully.
- If OB starts successfully, try invoking SAS Enterprise Miner again.
Operating System and Release Information
SAS System | SAS Integration Technologies | 64-bit Enabled HP-UX | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows XP Professional | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows NT Workstation | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Server | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Professional | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
64-bit Enabled Solaris | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
HP-UX IPF | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Linux on Itanium | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Linux | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
z/OS | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
OpenVMS Alpha | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
64-bit Enabled AIX | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
Tru64 UNIX | 9.1 TS1M3 | 9.1 TS1M3 SP4 |
*
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: | Problem Note |
Priority: | medium |
Topic: | Software Components ==> Object Spawner
|
Date Modified: | 2009-09-03 15:20:14 |
Date Created: | 2006-09-01 15:56:06 |