XCOM for Windows 11.6 SP03 successfully upgraded to 12.0 on Amazon Web Services (AWS) Windows server.
XCOM itself is working as expected.
However the StandaloneUI.bat XCOM GUI program is failing to start with:Error: XCOM_JAVA_HOME directory 'C:\Program Files\Java\jre1.8.0_441' not found
Control Panel > Programs and Features shows the Java 1.8 64-bit and XCOM 12.0 installs:
A silent install was used to do the installation.
XCOM™ Data Transport® for Windows 12.0
The XCOM_JAVA_HOME environment variable points to a Java directory that no longer exists, which can occur after a Java 64-bit update on the server.
Looking at the Environment Variable XCOM_JAVA_HOME setting "C:\Program Files\Java\jre1.8.0_441" (64-bit Java) and comparing to the "Programs and Features" screenshot it appears Oracle Java 8 64-bit is now at Update 481 i.e. the directory jre1.8.0_441 no longer exists and jre1.8.0_481 is present instead.
The XCOM "Installed On" date shows May 15 and the "Java 8 Update 481 (64-bit)" "Installed On" date shows February 12. So the Java Update has not occurred since the install.
Support speculated that the problem could be related to using a silent install with this scenario:
Support tried to recreate the problem with the same steps but could not get the install to run on server2 without using the LAX_VM parameter to force the use of a specific java.exe. The install runs successfully but ends up using the LAX_VM location for XCOM_JAVA_HOME.
Perhaps the root cause scenario is still similar and somehow the install ran successfully on server2 for the user.
The user confirmed that under "C:\Program Files\Java" the directory "jre1.8.0_441" does not exist and directory "jre1.8.0_481" does exist.
To resolve the problem the System Environment Variable XCOM_JAVA_HOME was updated to the current value C:\Program Files\Java\jre1.8.0_481.
Changing the Java install directory used by XCOM is also covered here: XCOM™ Data Transport® for Windows 12.0 > Administrating > Change the Java Path
Run a new command prompt to pick up the XCOM_JAVA_HOME System Environment Variable change, check its value using "echo %XCOM_JAVA_HOME%" and test StandaloneUI.bat.
The user was still having problems getting the XCOM_JAVA_HOME change to be visible after starting new command prompt and in the end restarted the server to be able to see it. This maybe be related to using a AWS Windows Server instance and perhaps logoff/logon might have avoided the need to restart.
The updated System Environment Variable value can also be checked with this registry query:reg query "HKLM\System\CurrentControlSet\Control\Session Manager\Environment" /v XCOM_JAVA_HOME
Example output:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment XCOM_JAVA_HOME REG_SZ C:\Program Files\Java\jre1.8.0_481