One of our end users just hit a strange problem. Unfortunately to fully explain it I will need to briefly describe our installer, so please bare with me
So, our installer consists of two parts. One (let's call it Core) contains all the binaries, and the other (let's call it Product) contains only some registry keys which customise the Core. Both parts of the installer are created by AI and the Core is a prerequisite of the Product (the Core package is embedded within the Product .exe). Moreover to correctly install the Core one needs to pass it some command line arguments. Without those arguments the Core will not get installed at all and subsequently the installation of the Product will fail. As you may imagine Product calls the installer of the Core with the correct set of commandline arguments.
This has always worked until recently an end-user found out that our software won't install on one of his PCs. After investigating the logs that he send us it turned out that the core was invoked without the command line arguments at all. The header of the installation of the Core looks:
Code: Select all
MSI (c) (F0:80) [08:01:29:063]: ******* RunEngine:
******* Product: C:\{18636258-CE6D-42DF-8DB4-566072C4C435}\DisplayLinkCore.msi
******* Action:
******* CommandLine:
Code: Select all
MSI (c) (94:EC) [11:51:43:299]: ******* RunEngine:
******* Product: C:\{733117AA-74C9-4780-BA02-3A63D8F8B977}\DisplayLinkCore.msi
******* Action:
******* CommandLine: ALLOW64BIT=No WIN2KSP4=Yes WINXPSP0=No WINXPSP1=No WINXPSP2=Yes WINSERVER2003=No VISTA=Yes
The problem is 100% reproducible on the end-user's particular system, so I wonder whether there is anything in the AI's bootstrapper which might have caused this behaviour? Maybe the bootstrapper reads some Windows Installer security configuration options and doesn't allow any command line parameters to be passed to the installers?
Any help will be greatly appreciated.
Thanks so much,
Rafal
FOLLOW US
Get the latest news in Application Packaging