Problem Note 42748: A validation failure occurs for a SAS® Workspace Server in the SAS® 9.2 environment
 |  |  |  |  |
In a SAS 9.2 environment, you might encounter a problem when you attempt to validate a SAS Workspace Server that is a member of a load-balanced cluster.
Consider a situation in which you have a two-machine setup that uses load-balanced SAS Workspace Servers in the following way:
- Machine 1: test1.test.com with alias test1
- Machine 2: test2.test.com with alias test2
In the configuration above, there are two SAS® Object Spawner definitions because there is a separate object-spawner definition for each machine (as is necessary in a load-balanced environment). The SAS Workspace Servers are defined separately, according to their aliases. However, they reside under the same logical-server context. Because this configuration uses the aliases as the host names, the logical workspace-server level will resemble the following structure:
Because the aliases are used to refer to the host names, the aliases are stored in the SAS® Metadata Repository as the host names of the object spawners and the servers test1 and test2. As a result, the default object spawner's start-up script contains the following lines, respectively:
Under these conditions, if you attempt to validate the servers in their load-balanced cluster, the attempt might be successful for the first SAS Workspace Server, but the validation fails for the second SAS Workspace Server. However, this failure does not necessarily indicate a problem with the server. Rather, the failure is likely related to the –dnsMatch option that is specified in the SAS Metadata Repository. This option forces the object spawner to match the definition that is in the metadata to the real, fully qualified host name. Therefore, the server name that is used for the purpose of load balancing contains the full host name rather than the alias. Validation fails because the object spawners (which communicate with one another in a load-balanced environment) only recognize the aliases, not the complete host name that they are now sharing.
You can either work around the problem or download a hot fix.
To circumvent this problem, use either of the following solutions:
- When you initially configure the system, use only full host names (no aliases).
- If your system is already configured, remove the -dnsMatch option in the object spawner's start-up file (either ObjectSpawner.bat or ObjectSpawner.sh). After you make this change, restart SAS® services.
- Change the configuration so that it points to the fully qualified host name. To do that, change the settings in the object spawner's start-up file(s) and in SAS® Management Console. After you make these changes, restart the SAS services.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS Integration Technologies | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M2 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows XP 64-bit Edition | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft® Windows® for x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 for x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2008 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2008 for x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Microsoft Windows XP Professional | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows 7 Enterprise 32 bit | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows 7 Enterprise x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows 7 Home Premium 32 bit | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows 7 Home Premium x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows 7 Professional 32 bit | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows 7 Professional x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows 7 Ultimate 32 bit | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows 7 Ultimate x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows Vista | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Windows Vista for x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| 64-bit Enabled AIX | 9.2 TS2M2 | 9.3 TS1M0 | ||
| 64-bit Enabled HP-UX | 9.2 TS2M2 | 9.3 TS1M0 | ||
| 64-bit Enabled Solaris | 9.2 TS2M2 | 9.3 TS1M0 | ||
| HP-UX IPF | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Linux | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Linux for x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| OpenVMS on HP Integrity | 9.2 TS2M2 | 9.3 TS1M0 | ||
| Solaris for x64 | 9.2 TS2M2 | 9.3 TS1M0 | ||
| z/OS | 9.2 TS2M2 | 9.3 TS1M0 | ||
A fix for this issue for Base SAS 9.21_M3 is available at:
http://ftp.sas.com/techsup/download/hotfix/HF2/B25.html#42748| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2013-01-15 14:36:27 |
| Date Created: | 2011-03-22 14:59:56 |