Error Unable To Load The Java Virtual Machine Sas 9.3
you run programs (for example: Proc javainfo; run;):ERROR: Unable to attach current thread" ERROR: Unable to load the java virtual machine" ERROR: Proc javainfo did not run correctly ERROR: The Java proxy is not responding. ERROR: The Java proxy's JNI call to start the VM failed. ERROR: Java failed to start during the SAS startup. These errors are typically related to issues with the Java Runtime Environment (JRE). To resolve these issues, follow these steps: Check your JREOPTIONS settings by submitting the following code in SAS:proc options option=jreoptions; run; Your log output should be similar to the following:proc options option=jreoptions; run; JREOPTIONS=( -DPFS_TEMPLATE=C:\Program Files\SASHome\SASFoundation\9.3\tkjava\sasmisc\qrpfstpt.xml -Djava.class.path=C:\PROGRA~1\SASHome\SASVER~1\eclipse\plugins\ SASLAU~1.JAR -Djava.security.auth.login.config=C:\Program Files\SASHome\SASFoundation\9.3\tkjava\sasmisc\sas.login.config -Djava.security.policy=C:\Program Files\SASHome\SASFoundation\ 9.3\tkjava\sasmisc\sas.policy -Djava.system.class.loader=com.sas.app.AppClassLoader -Dlog4j.configuration=file:/C:/Program%20Files/SASHome/ SASFoundation/9.3/tkjava/sasmisc/sas.log4j.properties -Dsas.app.class.path=C:\PROGRA~1\SASHome\SASVER~1\eclipse\ plugins\tkjava.jar -Dsas.ext.config=C:\Program Files\SASHome\SASFoundation\9.3\ tkjava\sasmisc\sas.java.ext.config -Dsas.jre.libjvm=C:\PROGRA~2\Java\JRE16~1.0_2\bin\client\jvm.dll -Dtkj.app.launch.config=C:\PROGRA~1\SASHome\SASVER~1\picklist -Xms128m ) Java Runtime Environment options NOTE: PROCEDURE OPTIONS used (Total process time): real time 0.01 seconds cpu time 0.00 seconds At the end of the log output, you should have a value that is similar to the following:-Dsas.jre.libjvm=C:\PROGRA~2\Java\JRE16~1.0_2\bin\client\jvm.dll Navigate to the location that is specified by -Dsas.jre.libjvm and verify the location of the jvm.dll file. To display the JRE version that is installed on your computer: Select StartRun and type cmd. Navigate to the bin directory by using the cd command. For example: C:\PROGRA~2\Java\JRE16~1.0_2\bin\ Following are examples of DOS commands that navigate to the bin location and verify the Java version:C:\>cd pro
Samples & SAS Notes Focus Areas SUPPORT License Assistance Manage My Software Account Downloads & Hot Fixes TRAINING & BOOKS Books Training Certification SAS Global Academic Program SAS OnDemand For Academics USERS GROUPS Advanced Search support.sas.com Knowledge Base Support Training & Books Store Support Communities Knowledge Base Products & Solutions System Requirements Install Center Third-Party Software Reference Documentation Papers Samples & SAS Notes Browse by Topic Search Samples Search Usage Notes Search Installation Notes Search Problem Notes Focus Areas Installation Note 44853: Errors occur at SAS® 9.3 start-up if the wrong JRE is used http://support.sas.com/documentation/cdl/en/hostwin/63047/HTML/default/n1khwpgqb1bv35n1b7gwvu8qdn3e.htm or if there is a problem with the existing JRE The following errors might occur on the Windows operating system if the wrong Java Runtime Environment (JRE) was used during the SAS 9.3 installation process or if something has happened to the JRE that is installed. ERROR: File(s) are missing from the Java repository. ERROR: Unable to initialize the ODS classpath during SAS startup. http://support.sas.com/kb/44/853.html ERROR: Exception text: For one or more plugin requests, no matching Plugins were found in repository. ERROR: Failed to attach to Java during SAS startup. ERROR: Unable to load the java virtual machine. ERROR: Proc javainfo did not run correctly. ERROR: The ODS initializer failed to instantiate during SAS startup. ERROR: Exception text: Assistive Technology not found: com.sun.java.accessibility.AccessBridge ERROR: Unable to load the Java Virtual Machine. Please see the installation instructions or system administrator. ERROR: The Java proxy is not responding. ERROR: The Java proxy's JNI call to start the VM failed. ERROR: Java failed to start during the SAS startup. Workarounds To debug these errors, try one or more of the following: Verify the JRE that was used during the installation process: Open the sassw.config file in Notepad. This file is located in the !SASHOME directory. The default location is C:\Program Files\SASHome\sassw.config. Here is an example of the contents of the sassw.config file: [properties] JREHOME=C:\Program Files (x86)\Java\jre1.6.0_24\bin\java.exe SASHOME=C:\Program Files\SASHome DPLMTREGLOC=C:\Program Files\SASHome\deploymntreg SASENVIRONMENTSURL= VJRHOME=C:\Program Files\SASHome\SASVersionedJarRepository Verify that the JRE is working correctly by performing the following: Click Start ► Run and type cmd. Navigate to the bin direc
Samples & SAS Notes Focus Areas SUPPORT License Assistance Manage My Software Account Downloads & Hot Fixes TRAINING & BOOKS Books Training Certification SAS Global Academic Program SAS OnDemand For Academics USERS GROUPS Advanced Search support.sas.com Knowledge Base Support Training & http://support.sas.com/kb/43/078.html Books Store Support Communities Knowledge Base Products & Solutions System Requirements Install Center Third-Party Software Reference Documentation Papers Samples & SAS Notes Browse by Topic Search Samples Search Usage Notes Search Installation Notes Search Problem Notes Focus Areas Installation Note 43078: When you invoke SAS® 9.3, error messages appear if a 64-bit JRE is used instead of a 32-bit JRE When you invoke SAS 9.3, these error messages might appear: ERROR: error unable The Java proxy is not responding. ERROR: Unable to load the Java Virtual Machine. Please see the installation instructions or system administrator. Or these messages might appear: ERROR: The Java proxy is not responding. ERROR: The Java proxy's JNI call to start the VM failed. A Java Runtime Environment (JRE) is required on every machine on which SAS is installed. The JRE must be 32-bit, even on 64-bit or x64 operating systems. error unable to The error messages shown above occur if a 64-bit JRE was used. When installing SAS, you can choose to install the recommended JRE or you can choose to use an existing JRE that is a later release than the recommended version. After the installation, you can change the release of the JRE that SAS uses by installing an alternate version of the JRE and altering a few key SAS configuration files. During installation, if you choose to specify an existing JRE, when you enter the path to the JRE via the SAS® Deployment Wizard, the version is checked but the capacity (in bytes) of the JRE is not checked. When installing SAS, if you specify the path to a 64-bit JRE, the error messages shown above appear when you try to invoke SAS 9.3. Operating System and Release InformationProduct FamilyProductSystemSAS ReleaseReportedFixed*SAS SystemN/AMicrosoft Windows Server 2003 Datacenter 64-bit Edition9.3 TS1M0Microsoft Windows Server 2003 Enterprise 64-bit Edition9.3 TS1M0Microsoft Windows Server 2003 for x649.3 TS1M0Microsoft Windows Server 2008 for x649.3 TS1M0Windows Vista for x649.3 TS1M064-bit Enabled AIX9.3 TS1M064-bit Enabled HP-UX9.3 TS1M064-bit Enabled Solaris9.3 TS1M0Linux for x649.3 TS1M0Solaris for x649.3 TS1M0z/OS9.3 TS1M0* 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. ERRO