Error Unable To Load The Java Virtual Machine Sas 9.2
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
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 http://support.sas.com/documentation/cdl/en/hostwin/63047/HTML/default/n1khwpgqb1bv35n1b7gwvu8qdn3e.htm Focus Areas Installation Note 44853: Errors occur at SAS® 9.3 start-up if the wrong JRE is used 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 http://support.sas.com/kb/44/853.html 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. 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
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead https://communities.sas.com/t5/SAS-GRAPH-and-ODS-Graphics/SAS-9-2x32-win7x64-JRE-6-14-10-months-w-o-working-ODS-gfx/td-p/21343 for Do you mean Find a Community Communities Welcome Getting Started Community Memo Community Matters Community Suggestion Box Have Your Say SAS Programming Base SAS Programming SAS Procedures ODS and Base Reporting SAS/GRAPH and ODS Graphics General SAS Programming SAS Studio Data Management SAS Data Management Analytics SAS Statistical Procedures error unable SAS/IML Software and Matrix Computations SAS Data Mining SAS Text and Content Analytics SAS Forecasting and Econometrics Mathematical Optimization, Discrete-Event Simulation, and OR Business Intelligence SAS Enterprise Guide Integration with Microsoft Office SAS Visual Analytics SAS Web Report Studio SAS Stored Processes Administration Administration and Deployment SAS Hot Fix Announcements SAS error unable to ITRM Learn SAS SAS Analytics U SAS Certification Customer Intelligence SAS Customer Intelligence SAS Intelligent Advertising Risk Management SAS Risk Management SAS Viya About SAS Viya SAS Visual Data Mining and Machine Learning Coding on SAS Viya SAS Visual Investigator Health Care and Pharma SAS in Health Care Related Fields SAS Drug Development SASware Ballot Ideas Regional Groups Special Interest Groups SAS Community Denmark SANZOC CoDe SAS German SAS Visual Analytics Nederland Singapore SAS Global Forum 2017 SAS Communities Library Home / SAS Programming / SAS/GRAPH and ODS Graphics / SAS 9.2x32, win7x64, JRE 6.14 - 10 months w/o work... SAS 9.2x32, win7x64, JRE 6.14 - 10 months w/o working ODS gfx Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page « Message Listing « Previous Topic Next Topic » Arsenio_Staer Contributor Posts:
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 00:55:32 GMT by s_ac15 (squid/3.5.20)