Balaji Pawar
Posts: 4
Joined: Thu Nov 14, 2024 8:36 am

Chained Prerequisite Issue with command line

Hi,
We have recently upgraded to advanced installer 22.8. As per the updated user guide, we are trying to add the chained prerequisite package with appropriate command. But the chained package is facing issue in CLI mode. The chained package is not getting installed. It is also showing network path issue in basic UI mode. And sometimes with full UI too it is getting stuck for a longer period of time.

We are using following command to add prerequisites:

call "AdvancedInstaller.com" /edit %AIP_PATH% /NewPrerequisite %DISPLAY_NAME% -type FeatureBased -prereq_path %Package_MSI_PATH% -ui_level Silent -cmd_basic_ui /qb -cmd_silent_ui /qn -search_type UpgradeCode -search_path %MSI_UPGRADE_code% -minversion %MIN_VERSION% -target_os Win64 -chained

We also have following queries:
-Is there any OS version related condition to run the exe made with 22.8 version of advanced installer?
-Is there any Min system spec related condition that is not mentioned in the user guide?
We are running these .exe on windows 10 and windows 11 OS with System spec being i7 10th gen 8GB RAM, 512GB Storage VMs.

Please look into this and do the needful.

Best regards,
Balaji
Catalin
Posts: 7664
Joined: Wed Jun 13, 2018 7:49 am

Re: Chained Prerequisite Issue with command line

Hello Balaji,

In our latest version, we have changed some things regarding the prerequisites support.

If possible, could you please try that and let me know if it helps with the issues you are encountering?

Regarding your questions, please allow me to address them below:
-Is there any OS version related condition to run the exe made with 22.8 version of advanced installer?
If you want, yes, you can set conditions for your EXE to run on specific OS systems. To do so, you can go to "Launch Conditions" page --> "System" tab --> "Supported Operating Systems".
-Is there any Min system spec related condition that is not mentioned in the user guide?
Not quite sure what you mean by this. If you mean the compatibility of packages created with Advanced Installer and specific OSs, then there are some limitations, yes. These can be seen here: Advanced Installer Requirements
We are running these .exe on windows 10 and windows 11 OS with System spec being i7 10th gen 8GB RAM, 512GB Storage VMs.
Everything should be working just fine, then. There is no limitation regarding packages built with our latest version and Windows 10/11.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Balaji Pawar
Posts: 4
Joined: Thu Nov 14, 2024 8:36 am

Re: Chained Prerequisite Issue with command line

Hi Catalin,

We are able to successfully build the installer, and the chained prerequisite is functioning as expected.

However, we have observed a difference in behavior compared to Advanced Installer version 20.8. In v20.8, both the prerequisite and the main package were installed to the same directory. In version 22.9.1, the prerequisite is always installed to its default location, even when the main package is installed to a custom path.

Our requirement is for both the prerequisite and the main package to be installed in the same directory, ensuring that all components reside in a common location.

Could you please advise how this can be achieved in the newer version?

Commands used:

Advanced Installer v20.8:

call "AdvancedInstaller.com" /edit %AIP_PATH% /NewPrerequisite %DISPLAY_NAME% -type FeatureBased -prereq_path %KERNEL_MSI_PATH% -search_type UpgradeCode -search_path %MSI_UPGRADE_code% -minversion %MIN_VERSION% -cmd_line "/qn LICENSE_SERVER=[LICENSE_SERVER] APPDIR=\"%APPDIR_VALUE%\"" -target_os Win64


Advanced Installer v22.9.1:

call "AdvancedInstaller.com" /edit %AIP_PATH% /NewPrerequisite %DISPLAY_NAME% -type FeatureBased -prereq_path %KERNEL_MSI_PATH% -ui_level Silent -cmd_basic_ui "/qn TARGETDIR=""[APPDIR]""" -cmd_silent_ui "/qnTARGETDIR=""[APPDIR]""" -search_type UpgradeCode -search_path %MSI_UPGRADE_code% -minversion %MIN_VERSION% -target_os Win64 -chained


This command builds the installer successfully, but it does not meet our requirement of installing the prerequisite in the same directory as the main package. We also tried using APPDIR and INSTALLDIR instead of TARGETDIR, but the behavior remained unchanged.

Any guidance on this would be greatly appreciated.

Thanks and regards,
Balaji
Catalin
Posts: 7664
Joined: Wed Jun 13, 2018 7:49 am

Re: Chained Prerequisite Issue with command line

Hello Balaji,

If the prerequisite is also built with Advanced Installer, in order to have them installed in the same directory, we have to pass (to the prerequisite) the following command line:

APPDIR="[APPDIR]"

Via this command line, we basically tell the prerequisite to be installed in the same location as the APPDIR of the main package.

If this does not work, do you think you can reproduce this in a sample project and forward that to me (by email at support at advancedinstaller dot com) so I can run some tests on my end? I'm asking for a sample because I was not able to reproduce this when I tested the scenario.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”