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
- :
- Windows Downloaded JVM Not Detected
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 23, 2012
10:25 AM
Windows Downloaded JVM Not Detected
I think InstallAnywhere 2011 SP3 breaks detection of downloaded JVM on Windows. (It works on Linux.)
I cannot figure out how to test if it is SP3 since I don't know how to retro to SP2 and my last saved installer was 01-29 and SP3 was installed on 01-26.
Using "ctrl" key while running Windows installer shows debug log that confirms that my URL is good and my JVM is downloaded and extracted correctly. InstallAnywhere then give error, "could not find a valid java virtual machine to load". Besides confirming JVM is good by running successfully on Linux, I also confirmed good downloaded JVM by switching option to "Don't search for VM; download from URL".
So I can only conclude that InstallAnywhere SP3 has a bug for detected a downloaded JVM. Can anyone else confirm? Can Flexera test and provide a fix?
Here are some of my project settings that are interest:
- Build > Build Configurations > Build Targets > Windows:
Without VM
Search for VM; if not found, download from URL
JVM Search Settings: (tried them all)
spec files from Flexera
Windows spec file without ctl-m line feeds
even no spec file which documentation says will allow any JVM
- Project > JVM Settings > Installer Settings:
Installer Valid VM List: 1.4+
Bundled / Downloaded Virutal Machine:
Install Bundled / Downloaded Virtual Machine:
Only when a compatible VM is not found in the system
VM Install Folder: User Install Folder/JRE
Do not remove bundled / downloaded VM when uninstalling
- Project > JVM Settings > Search Panel Settings:
General: Use installer's valid VM list (1.4+)
Windows: (default settings)
- Project > Platforms > Windows:
Launder JVM Selection:
tried all of them but want "Use 64bit JVM, if not available use 32 bit JVM"
I cannot figure out how to test if it is SP3 since I don't know how to retro to SP2 and my last saved installer was 01-29 and SP3 was installed on 01-26.
Using "ctrl" key while running Windows installer shows debug log that confirms that my URL is good and my JVM is downloaded and extracted correctly. InstallAnywhere then give error, "could not find a valid java virtual machine to load". Besides confirming JVM is good by running successfully on Linux, I also confirmed good downloaded JVM by switching option to "Don't search for VM; download from URL".
So I can only conclude that InstallAnywhere SP3 has a bug for detected a downloaded JVM. Can anyone else confirm? Can Flexera test and provide a fix?
Here are some of my project settings that are interest:
- Build > Build Configurations > Build Targets > Windows:
Without VM
Search for VM; if not found, download from URL
JVM Search Settings: (tried them all)
spec files from Flexera
Windows spec file without ctl-m line feeds
even no spec file which documentation says will allow any JVM
- Project > JVM Settings > Installer Settings:
Installer Valid VM List: 1.4+
Bundled / Downloaded Virutal Machine:
Install Bundled / Downloaded Virtual Machine:
Only when a compatible VM is not found in the system
VM Install Folder: User Install Folder/JRE
Do not remove bundled / downloaded VM when uninstalling
- Project > JVM Settings > Search Panel Settings:
General: Use installer's valid VM list (1.4+)
Windows: (default settings)
- Project > Platforms > Windows:
Launder JVM Selection:
tried all of them but want "Use 64bit JVM, if not available use 32 bit JVM"
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 22, 2012
11:55 AM
Flexera confirmed this as a bug and is tracked as "IOA-000072208".