InstallerBldr
Posts: 13
Joined: Thu Nov 09, 2017 1:26 am

Command line arguments via Bootstrapper Exe

Fri Nov 17, 2017 1:41 am

Hi, would appreciate a hand with the following behavior.

Using a trial Enterprise version of IA v14.4

Builds: Single EXE setup (resources inside)

Themes: Style9green, Settings: Use Enhanced User Interface: Always (install, uninstall and maintenance)

run the following:
.\"BootstrapperInstaller.exe" /i \\ /l*v "InstallLog.txt"

InstallLog.txt contains the following:

=== Verbose logging started: 11/16/2017 16:25:41 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Users\InstallerBldr\Desktop\Advanced Installer Proof of Concept\BootstrapperInstaller.exe ===
MSI (c) (78:90) [16:25:41:403]: Note: 1: 2203 2: \ 3: -2147287037
MSI (c) (78:90) [16:25:41:403]: MsiOpenPackageEx is returning 3.
=== Verbose logging stopped: 11/16/2017 16:25:41 ===

Does this still relate to the Enhanced UI issues from 2012?

viewtopic.php?f=2&t=23711&p=60494&hilit ... eEx#p60494
viewtopic.php?f=2&t=23076&p=58128#p58106
https://www.advancedinstaller.com/user- ... ed-ui.html

Or is there something I'm missing with my command line arguments to the bootstrapper? We need to be able to pass command line args down into the internal bundled msi in order for all our legacy test automation to work. Getting some advice on this would be great thanks.

Daniel
Posts: 8237
Joined: Mon Apr 02, 2012 1:11 pm
Contact:  Website

Re: Command line arguments via Bootstrapper Exe

Fri Nov 17, 2017 4:22 pm

Hello,

Thank you for your post. Actually after analyzing it I noticed that our EXE setup article is not very clear in this regards. We will try to update it as soon as possible. Thank you for bringing this to our attention.

When launching the setup in install mode you should simply use a command line like this:

Code: Select all

.\"BootstrapperInstaller.exe" /l*v "InstallLog.txt"
There is no need to specify the MSI execution install mode command (/i) - this is the default execution mode used by our EXE setup-, nor specify the extracted MSI path ("\\"). The MSI execution modes (and the path to the extracted MSI - "\\") should be explicitly set by command line only when using a different execution mode that the install one: admin install (/a), uninstall (/x), repair (/f), etc.

Check the msiexec article for more details.


All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”