XCOM for Windows 12.0 installer exits immediately (3004)
Article ID: 273755
Updated On:
Products
Issue/Introduction
Running the XCOM for Windows 12.0 installer XCOM_12_0_23053.exe on Windows Server 2019.
The installer launched for a few seconds and exited immediately.
Using Windows Debug captured these errors:
The process 'C:\Temp\XCOM_12_0_23053.exe' exited with exit code 3004. The creation time for the exiting process was 0x01d9e78baf8939bd.
The process 'C:\Temp\2\I1694751511\Windows\XCOM_12_0_23053.exe' exited with exit code 3004. The creation time for the exiting process was 0x01d9e78bb1808d3a.
Environment
XCOM for Windows 12.0
Resolution
There have been some compatibility issues reported between certain versions of InstallAnywhere (used for the XCOM installation), Java and Windows versions. Possibly later versions of Java 1.8 trigger the problem.
The default Java version on the server is used by the installer and can be found by typing "java.exe -version" from a command prompt.
To force the use of another Java version, the installer can be started with the LAX_VM parameter i.e.
XCOM_12_0_23053.exe LAX_VM "JRE_INSTALL_DIR\bin\java.exe"
That is per this article: XCOM install error "Flexeraaw7$aaa: Windows DLL failed to load"
The user found that the default Java version being picked up was 17 i.e. they found the directory "E:\Program Files\Microsoft\jdk-17.0.8.101-hotspot\bin" in the System PATH.
Java 17 is not compatible with XCOM or its installer which both require Java 1.8 (XCOM™ Data Transport® for Windows 12.0 > Installing > Prepare for Installation > Review the Software Requirements).
After removing the above directory entry, the software installed correctly.
Moving forward it is suggested to restore Java 17 to the system PATH to avoid impacting any other applications that use it and for future XCOM installations, the above LAX_VM parameter can be used.
Additional Information
Feedback
