Usage Note 38386: Resolving Java Runtime Environment (JRE) errors in SAS® 9.2
When you use JRE in SAS 9.2, you might encounter errors similar to the following:
ERROR: Unable to attach current thread" ERROR: Unable to load the java virtual machine"
ERROR: The Java proxy is not responding. ERROR: The Java proxy's JNI call to start the VM failed.
ERROR: Proc javainfo did not run correctly
To resolve these issues with JRE, use the following steps. Note: Click the Full Code tab, above, for an automated version of these steps using SAS code.
- Double-check your JREOPTIONS settings by submitting the following code:
proc options option=jreoptions;
run;
At the beginning of the JREOPTIONS output in the SAS log, a value similar to the following appears:
-Dsas.jre.libjvm=C:\PROGRA~1\Java\JRE15~2.0_1\bin\client\jvm.dll
- Navigate to this location and check that the jvm.dll file is saved there.
- At a command prompt, navigate to the bin directory found in Step 1 and enter java –version to display the JRE version that is installed on your computer. For most versions of Windows, ensure that you have JRE version 5. Windows 7 or Windows 2008 Server require JRE version 6 (32-bit). See SAS 9.2 (TS2M3) Support for Java Runtime Environments for details.
- Open your SAS configuration file, which is located in c:\program files\sas\sasfoundation\9.2\nls\en\sasv9.cfg.
- In the sasv9.cfg file, locate the -jreoptions line. Ensure that all of the text is on one line of this file and that spaces are inserted at the start of each option. Each option begins with a hyphen (-).
- Look for error messages in the Java log located in C:\Documents and Settings\your-user-ID\Application Data\SAS\LOGS.
If necessary, reinstall JRE from Third-Party Software Requirements for Use with SAS® Software and Applications.
If the above steps do not resolve your issue, send an email message to SAS Technical Support. In your email, include your sasv9.cfg file, the output from Step 1, and any Java logs from Step 6.
Operating System and Release Information
SAS System | Base SAS | Windows Vista | 9.21 | | 9.2 TS2M0 | |
Microsoft Windows XP Professional | 9.21 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Standard Edition | 9.21 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.21 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.21 | | 9.2 TS2M0 | |
Microsoft® Windows® for x64 | 9.21 | | 9.2 TS2M0 | |
Microsoft Windows XP 64-bit Edition | 9.21 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.21 | | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.21 | | 9.2 TS2M0 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.21 | | 9.2 TS2M0 | |
*
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.
Please run the code below to automate steps 1-5 of the debugging steps of this note.
Look in the log for obvious problems or send the log to support@sas.com for analysis.
If you see these errors in the log from the PIPE datasteps:
Stderr output:
There is not enough space on the disk.
Please use
SAS Note 41863
for assistance.
proc options option=jreoptions; run;
data _null_;
jvmdll=scan(substr(getoption('jreoptions'),find(getoption('jreoptions'),'Dsas.jre.libjvm','i')),2,'=-');
jvmpath=substr(jvmdll,1,length(jvmdll)-7)||'..\';
jrever=substr(jvmdll,1,length(jvmdll)-7)||'..\java.exe -version';
call symput('jvmdll',jvmdll);
call symput('jvmpath',jvmpath);
call symput('jrever',jrever);
run;
filename xdir pipe "dir &jvmdll";
data _null_;
infile xdir firstobs=5 obs=6;
input;
put _infile_;
run;
filename xdir pipe "dir &jvmpath";
data _null_;
infile xdir;
input;
put _infile_;
run;
filename jrever pipe "&jrever";
data _null_;
infile jrever;
input;
put _infile_;
run;
proc javainfo; run;
Date Modified: | 2010-10-27 09:54:43 |
Date Created: | 2010-01-13 10:35:55 |