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 incomplete with "Custom" option of console installer (-i console)
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
Dec 27, 2017
05:22 AM
Installation incomplete with "Custom" option of console installer (-i console)
Hello Team,
We are using InstallAnywhere to create console based installer along with GUI & silent installers.
While running console installer I am selecting the option "Custom" and selecting required modules after "Custom" option. Then installation continues and finishes with success message. But if I go to the installed folder and check , required folders are missing ,only few folders are available there leaving installation incomplete.
Whether anybody faced the issue with "Custom" option , please help me to resolve this issue.
Thanks
Harsha.
We are using InstallAnywhere to create console based installer along with GUI & silent installers.
While running console installer I am selecting the option "Custom" and selecting required modules after "Custom" option. Then installation continues and finishes with success message. But if I go to the installed folder and check , required folders are missing ,only few folders are available there leaving installation incomplete.
Whether anybody faced the issue with "Custom" option , please help me to resolve this issue.
Thanks
Harsha.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 12, 2018
01:49 AM
probably you have to set required OS types in install phase.
Enable a install log to trap the issue.
before running .bin file run export LAX _DEBUG=true for debugging
Enable a install log to trap the issue.
before running .bin file run export LAX _DEBUG=true for debugging