https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/726819#M21803 <P>Migration to Windows 2016 should not be the cause.<BR />Try manually stopping SAS and reboot the server machine.</P><P>SAS should start on its own.<BR />Have a look at the logs .</P> Tue, 16 Mar 2021 16:19:21 GMT Sajid01 2021-03-16T16:19:21Z https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/726805#M21802 <P>We recently migrated to a Windows 2016 server, and now many of our reports are failing with the following error:&nbsp;&nbsp;ERROR: Unable to attach current thread.<BR />ERROR: Unable to load the Java Virtual Machine. Please see the installation instructions or system administrator.</P><P>&nbsp;</P><P>I've run some of the suggestions on similar problems, but I'm not finding a solution for Windows 2016.&nbsp; The proc javainfo does not run correctly.&nbsp; The jreoptions output follows.&nbsp; I did check and the jvm.dll path is correct.</P><P>&nbsp;</P><P>SAS (r) Proprietary Software Release 9.4 TS1M6</P><P>JREOPTIONS=( -DPFS_TEMPLATE=d:\SASHome\x86\SASFoundation\9.4\tkjava\sasmisc\qrpfstpt.xml<BR />-Djava.class.path=d:\SASHome\SASVER~1\eclipse\plugins\SASLAU~1.JAR<BR />-Djava.security.auth.login.config=d:\SASHome\x86\SASFoundation\9.4\tkjava\sasmisc\sas.login.config<BR />-Djava.security.policy=d:\SASHome\x86\SASFoundation\9.4\tkjava\sasmisc\sas.policy<BR />-Djava.system.class.loader=com.sas.app.AppClassLoader<BR />-Dlog4j.configuration=file:/D:/SASHome/x86/SASFoundation/9.4/tkjava/sasmisc/sas.log4j.properties<BR />-Dsas.app.class.path=d:\SASHome\SASVER~1\eclipse\plugins\tkjava.jar<BR />-Dsas.ext.config=d:\SASHome\x86\SASFoundation\9.4\tkjava\sasmisc\sas.java.ext.config<BR />-Dsas.jre.libjvm=C:\Program Files (x86)\Java\jre1.8.0_251\bin\client\jvm.dll<BR />-Dtkj.app.launch.config=d:\SASHome\SASVER~1\picklist -Xms128m -Xmx128m )<BR />Specifies the Java Runtime Environment options for SAS.</P><P>&nbsp;</P> Tue, 16 Mar 2021 15:28:35 GMT https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/726805#M21802 clbroyles55 2021-03-16T15:28:35Z https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/726819#M21803 <P>Migration to Windows 2016 should not be the cause.<BR />Try manually stopping SAS and reboot the server machine.</P><P>SAS should start on its own.<BR />Have a look at the logs .</P> Tue, 16 Mar 2021 16:19:21 GMT https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/726819#M21803 Sajid01 2021-03-16T16:19:21Z https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/727541#M21840 I tried booting the server, and it didn't solve the problem. Thu, 18 Mar 2021 19:32:17 GMT https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/727541#M21840 clbroyles55 2021-03-18T19:32:17Z https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/727547#M21841 <P>Sorry to hear that.<BR />In your situation I would seek help from SAS Tech Support.<BR />Suggest the same.</P> Thu, 18 Mar 2021 19:48:12 GMT https://communities.sas.com/t5/Administration-and-Deployment/Unable-to-load-java-virtual-machine-Windows-2016-Server/m-p/727547#M21841 Sajid01 2021-03-18T19:48:12Z