- Revenera Community
- :
- FlexNet Operations
- :
- FlexNet Operations Knowledge Base
- :
- FNO 2022.R1 installation failed with latest Java JDK on Windows Server 2022
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
FNO 2022.R1 installation failed with latest Java JDK on Windows Server 2022
FNO 2022.R1 installation failed with latest Java JDK on Windows Server 2022
Introduction: When trying to install FlexNet Operation 2022.R1 on Windows Server 2022 the installation failed with the latest Java JDK 8u351
Flexeraaxf$aaa: C:\Users\Administrator\AppData\Local\Temp\2\I1677784313\Windows_Pure_64_Bit\resource\iawin32.dll not found at Flexeraaxf.af(Unknown Source) at Flexeraaxf.aa(Unknown Source) at com.zerog.ia.installer.LifeCycleManager.init(Unknown Source) at com.zerog.ia.installer.LifeCycleManager.executeApplication(Unknown Source) at com.zerog.ia.installer.Main.main(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.zerog.lax.LAX.launch(Unknown Source) at com.zerog.lax.LAX.main(Unknown Source)
Solution:
1. Make sure the Java KDK or JRE is a 64bit version only.
2. If using jdk-8u351-windows-x64.exe which has issues with the FNO installer (InstallShield did not support the latest version of JDK), can you downgrade to Java 64-bit 8u301 or earlier as a temporary fix until the latest JDK tested with FNO installer.
3. Or still want to use the same JDK then here is the workaround for Windows Server 2022
Report an older OS by setting a system variable; PowerShell example:[System.Environment]::SetEnvironmentVariable("JAVA_TOOL_OPTIONS", '-Dos.name="Windows Server 2016"', "Machine")
-> Proceed with FNO installation
-> Delete the system variable
[System.Environment]::SetEnvironmentVariable("JAVA_TOOL_OPTIONS", ", $null ,"Machine")
Outcome: Downgrading to use jdk-8u301-windows-x64.exe fixed the issue.