This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Installation fails on Windows 2012 R2
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jul 17, 2014
09:58 AM
Installation fails on Windows 2012 R2
Hi Folks,
Installer created with IA 2012 fails on Windows 2012 R2.
Error below:
Flexeraawy$aaa: Windows DLL failed to load
at Flexeraawy.af(Unknown Source)
at Flexeraawy.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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.zerog.lax.LAX.launch(Unknown Source)
at com.zerog.lax.LAX.main(Unknown Source)
Does IA2012 support Windows 2012 R2?
Or what is the workaround?
Thanks,
Kannan
Installer created with IA 2012 fails on Windows 2012 R2.
Error below:
Flexeraawy$aaa: Windows DLL failed to load
at Flexeraawy.af(Unknown Source)
at Flexeraawy.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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.zerog.lax.LAX.launch(Unknown Source)
at com.zerog.lax.LAX.main(Unknown Source)
Does IA2012 support Windows 2012 R2?
Or what is the workaround?
Thanks,
Kannan
(4) Replies
‎Jul 17, 2014
10:54 AM
I'm not sure whether there is a workaround for that. However, I can confirm that InstallAnywhere 2012 does not have support for Windows Server 2012 R2 (which shipped after both InstallAnywhere 2012 and the service pack for InstallAnywhere 2012).
Support for Windows Server 2012 R2 was introduced in InstallAnywhere 2013. You may want to download the eval version of InstallAnywhere 2013 and see if the issue is resolved.
Support for Windows Server 2012 R2 was introduced in InstallAnywhere 2013. You may want to download the eval version of InstallAnywhere 2013 and see if the issue is resolved.
‎Aug 14, 2014
02:54 AM
KANNANEMC wrote:
Thanks for the update DebbieL.
We were able to install our previous builds ( built with IA2012) on Windows 2012 R2.
We tried IA2013 trial version. It again failed with the same error.
Regards,
Kannan
I am also getting the following error when installing on Windows 2012 R2 usinf IA2012
"Windows DLL failed to load"
I would like to know how was this problem resolved. I do not receive this error when installing on windows 2012
Any help would be appreciated. Also we noted that this error goes away if we provide a LAX_VM parameter to the installer that point to java 170_51 or earlier
The moment LAX_VM is set to later java versions it starts throwing the error on Windows 2012.
Regards,
Nitin
‎Jan 30, 2015
03:16 PM
nitinsingal wrote:
I am also getting the following error when installing on Windows 2012 R2 usinf IA2012
"Windows DLL failed to load"
I would like to know how was this problem resolved. I do not receive this error when installing on windows 2012
Any help would be appreciated. Also we noted that this error goes away if we provide a LAX_VM parameter to the installer that point to java 170_51 or earlier
The moment LAX_VM is set to later java versions it starts throwing the error on Windows 2012.
Regards,
Nitin
This issue was not addressed until Hotfix C for IA2013. I found a workaround to be setting compatibility in the install executable file properties to Windows 8.