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: Error finding Win32 VM pack - Out of Memory
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
‎Sep 29, 2016
05:01 PM
Error finding Win32 VM pack - Out of Memory
I started getting this error today when I tried to build the windows config of our installer from a command line. I was building with no problems earlier in the day. I made no configuration changes.
Does anyone have any idea what might have gone wrong, or where it should be looking for the missing VM?
This is from the buildlog.xml:
Does anyone have any idea what might have gone wrong, or where it should be looking for the missing VM?
This is from the buildlog.xml:
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 30, 2016
09:53 AM
OK, I can't understand why the build executable suddenly stopped working. In my "InstallAnywhere 2014 SP1/resource/installer_vms" directory are two oracle .vm files (32 & 64 bit). Does anybody know why the build can find these vms?
I've increased the max heap in InstallAnywhere.lax file by 4 times and the result is the same.
Anybody from Flexera listening?
I've increased the max heap in InstallAnywhere.lax file by 4 times and the result is the same.
Anybody from Flexera listening?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 03, 2016
11:47 AM
Seriously is anyone from Flexera watching or listening?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 24, 2017
08:55 AM
Did you find idea about this issue?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 04, 2017
07:58 AM
Hi,
Did you tried increasing max heap size? lax.nl.java.option.java.heap.size.max in\InstallAnywhere.lax
--Jerome
Did you tried increasing max heap size? lax.nl.java.option.java.heap.size.max in
--Jerome