Problem Note 37130: An error is generated when some SAS Web applications fail to execute properly
If the correct path to the java.exe file is not defined properly in your operating environment, the SAS Web applications that use SAS Remote Services might fail to execute. This problem occurs even though SAS Remote Services seems to start properly.
When the problem happens, the following error appears in the SAS Web Application Server's stdout log file:
[WARN ] sas.services.deployment.RMIConfiguration -
A service registry is not available on "hostname:5099" and the
preference is to not start a registry.
java.rmi.ConnectException: Connection refused to host:
hostname; nested exception is:
java.net.ConnectException: Connection refused: connect
To correct the problem, verify that the JAVA_HOME environment variable is set at the operating-system level. In addition, ensure that the environment variable refers to the correct Java Development Kit installation that is required by the SAS
® System.
Example
JAVA_HOME= C:\jdk1.4.2_05
To set the JAVA_HOME environment variable in Windows operating environments:
- Right-click My Computer on your desktop.
- Select Properties.
- Click the Advanced tab.
- Click Environment Variables at the bottom of the window.
- Under System Variables, click New.
- For the variable name, enter JAVA_HOME.
Note: This variable name is case sensitive.
- For the variable value, enter the path to your java.exe file. That pathname should be similar to the following example pathname:
C:\jdk1.4.2_05
- Click OK.
If SAS Remote Services is running as a Windows service, you also need to specify the full pathname to the Java executable in the wrapper.conf file. The wrapper.conf file is located in the \Lev1\web\Deployments\RemoteServices\WEB-INF\conf directory. To specify the full pathname, change the line wrapper.java.command=java, as follows:
wrapper.java.command=%JAVA_HOME%\bin\java
After you make all of the changes, restart SAS Remote Services, and then restart the Web application server.
Operating System and Release Information
| SAS System | SAS Enterprise BI Server | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2008 | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | |
| Windows Vista | 9.1 TS1M3 SP4 | |
| 64-bit Enabled AIX | 9.1 TS1M3 SP4 | |
| 64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | |
| 64-bit Enabled Solaris | 9.1 TS1M3 SP4 | |
| HP-UX IPF | 9.1 TS1M3 SP4 | |
| Linux | 9.1 TS1M3 SP4 | |
| Linux on Itanium | 9.1 TS1M3 SP4 | |
| Solaris for x64 | 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 |
| Date Modified: | 2011-10-17 14:56:53 |
| Date Created: | 2009-09-09 13:52:45 |