Unable to load Java Virtual Machine after upgrade to SAS 9.4M8

[stevo642]

I just updated to SAS 9.4 (TS1M8) from 9.4 (TS1M7) on Win 10 (X64_10PRO WIN 10.0.19041 Workstation) with up-to-date Windows software.

I get the following errors when invoking PROC SGPLOT.

• ERROR: Unable to attach current thread.
• ERROR: Unable to load the Java Virtual Machine. Please see the installation instructions or system administrator.
• ERROR: The Java child process terminated unexpectedly: status 1

A couple of additional notes:

• I had to run the compatibility troubleshooter to get setup.exe running in the Software Depot. The compatibility troubleshooter selected "Win XP (SP3)" mode. It completed smoothly.
• I saw similar posts but they were from several years ago so I thought I'd start a new one.

Any info appreciated...

[SASKiwi]

I suggest you run this and post the SAS log:

proc javainfo;
run;

Opening a Tech Support track is your best option to get this fixed. My understanding is that a major Java upgrade happens when going to M8.

[stevo642]

Thank you. Ran the code. Results follow. I will also post to Support Track.

Log file from "proc javainfo;run;" attached as .txt file.

Relevant messages:

ERROR: Proc javainfo did not run correctly.
ERROR: The Java child process terminated unexpectedly: status 1.
1          proc javainfo;run;

[SASKiwi]

That doesn't look healthy at all and suggests that the Java update did not work correctly. Tech Support should be able to offer guidance on next steps. One option might be to deinstall SAS completely and do a clean install of M8.

[stevo642]

Thank you, again

I also sent before/after sasv9.cfg files to Support Track

Other SAS PROCS seem to be running well. It seems to only be Java.

[SASKiwi]

M8 was only released in Jan 2023, so it's possible you've got a problem no one else has had yet. I suggest you wait for TS guidance. 

[rakotovao]

On unix we have added these lines to the file /SAS/software/SASFoundation/9.4/bin/sasenv_local

to correct these problems.

LIBPATH=$LIBPATH:/SAS/software/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/default/

export LIBPATH

[stevo642 · Accepted solution]

It turns out at the end of my sasv9.cfg -JREOPTIONS, I had two -XMX settings.

Deleting one fixed things. (I deleted the smaller value, -xmx512m)

-JREOPTIONS=(
        -DPFS_TEMPLATE=!SASROOT\tkjava\sasmisc\qrpfstpt.xml
        -Djava.class.path=C:\APPS\SAS94\SASVER~1\eclipse\plugins\SASLAU~1.JAR
        -Djava.security.auth.login.config=!SASROOT\tkjava\sasmisc\sas.login.config
        -Djava.security.policy=!SASROOT\tkjava\sasmisc\sas.policy
        -Djava.system.class.loader=com.sas.app.AppClassLoader
        -Dlog4j.configurationFile=file:/C:/APPS/SAS94/SASFoundation/9.4/tkjava/sasmisc/sas.log4j.properties
        -Dsas.app.class.path=C:\APPS\SAS94\SASVER~1\eclipse\plugins\tkjava.jar
        -Dsas.ext.config=!SASROOT\tkjava\sasmisc\sas.java.ext.config
        -Dsas.jre.libjvm=C:\APPS\SAS94\SASPRI~1\9.4\jre\bin\server\jvm.dll
        -Dtkj.app.launch.config=C:\APPS\SAS94\SASVER~1\picklist
        -Xms1024m
        -Xmx1024m
        -Xmx512m
        )

Thanks, everybody !!