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: Uninstaller encountered no JVM found problem
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
‎Nov 07, 2008
09:58 AM
Uninstaller encountered no JVM found problem
We encountered this problem (see below) for uninstaller when we removed java from the path
===========================================
No Java virtual machine could be found from your PATH
environment variable. You must install a VM prior to
running this program.
===========================================
We looked further and find the value of "lax.nl.current.vm=jre/jre/bin/java" in "Uninstall-FileNetQuickrServices-1.0.lax"
is incorrect. it should be
"lax.nl.current.vm=../jre/jre/bin/java"
Note the ../ here
the workaround is to include Java in the path. But We do bundle JVM when building our installer so this really should not be needed...
So is this a IA bug, a JVM bug,
or We forget to put some properties there?
This happened to many unix platforms like HP. I have not tested Windows and other platforms yet.
I appreciate your quick response...
===========================================
No Java virtual machine could be found from your PATH
environment variable. You must install a VM prior to
running this program.
===========================================
We looked further and find the value of "lax.nl.current.vm=jre/jre/bin/java" in "Uninstall-FileNetQuickrServices-1.0.lax"
is incorrect. it should be
"lax.nl.current.vm=../jre/jre/bin/java"
Note the ../ here
the workaround is to include Java in the path. But We do bundle JVM when building our installer so this really should not be needed...
So is this a IA bug, a JVM bug,
or We forget to put some properties there?
This happened to many unix platforms like HP. I have not tested Windows and other platforms yet.
I appreciate your quick response...
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 07, 2008
10:27 AM
Well, IA installers are Java-based, which means they need a JVM in order to properly operate. The same applies to uninstallers. Usually, IA is used for Java-based applications, which means a JVM is always installed, which will be used by the uninstaller. So in you case, you don't install a JVM, but this one is used only at install time, if you remove all JVM from the path, having this message when attempting to uninstall is normal, IA works as designed...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 07, 2008
12:35 PM
Well, we do bundle JVM in our installer. And installer works without external JVM. the issue is the config file generated by IA miss a "../" for java path. and then uninstaller could not find the JVM.
So not sure this is a IA bug, JVM bug?
So not sure this is a IA bug, JVM bug?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 07, 2008
03:12 PM
It looks like the exact same issue described here: http://community.acresso.com/showthread.php?t=183771&highlight=uninstall
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 10, 2008
03:53 AM
This is only HP-specific, when the bundled jre is an JDK.
When using a JRE then uninstall works.
When using a JRE then uninstall works.