AI_VerifyPrereq returned actual error code 1602

[rmoc]

I am trying to install my setup without user interaction. However, I am failing again due to the prerequisite.

I start the exe via a Powershell console (with administrator rights) as follows:

Code: Select all

.\TestSubMSI.exe /exenoui /qn /l*v install.txt

The installation ends with the following error:

Code: Select all

CustomAction AI_VerifyPrereq returned actual error code 1602 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 03:12:02: AI_VerifyPrereq. Return value 2.
Action ended 03:12:02: INSTALL. Return value 2.

Installation in the same console directly via MSIEXEC works without any problems:

Code: Select all

msiexec.exe /i "<setup path>\Microsoft OLE DB Driver for SQL Server\msoledbsql.msi" IACCEPTMSOLEDBSQLLICENSETERMS=YES /qn /l*v install.txt

Log file:

install.txt

(152.47 KiB) Downloaded 12 times

Test project:

TestSubMSI.zip

(10.27 KiB) Downloaded 19 times

You can download the “SQL Server OLE DB Driver 18” from here https://go.microsoft.com/fwlink/?linkid ... lcid=0x409
Please copy it to the folder “Prerequisites\SQL Server OLE DB Driver 18”.

[Catalin]

Hello Rene,

Thank you for the provided resources.

I have tested this on my end and can confirm the behavior.

I have opened a ticket with high priority so this can be fixed as soon as possible.

I really want to apologize for the inconvenience this has caused - especially as this is not the only opened ticket you have going on.

Until this is fixed, as per my tests, if you schedule the prerequisite to run "before main package", then the installation is successful, so you might want to schedule it as such. The only drawback of "before main package" prerequisites is the fact that they require an EXE setup package, which you already have, so that should not be a problem.

Best regards,
Catalin

[rmoc]

Hello Catalin,

First of all, I would like to thank you and your entire support team. You are doing a really great job.

We are currently introducing the Advanced Installer setup step by step, and understandably, a few issues come up here and there.

The condition for the EXE project itself is not the problem. Since the subpackage depends on the feature selection and is also dependent on the installation of the main package, I am forced to launch it at the very end.

Best regards,
René