Hello,
My project is configured for an online / web install, whereby the bootstrapper downloads the MSI from a URL. I am also enforcing the "active Internet connection" prerequisite.
Assuming the "active Internet connection" prereq is satisfied, I am wondering if it is possible for the bootstrapper to validate the MSI location (URL) before invoking msiexec.exe. Currently, if the MSI cannot be located (due to an invalid URL or perhaps the server hosting the MSI has crashed) the user receives the following message from Windows Installer:
"This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."
The log file contains:
=== Verbose logging started: 4/2/2010 11:31:44 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: C:\windows\system32\msiexec.exe ===
MSI (c) (98:D4) [11:31:44:390]: Resetting cached policy values
MSI (c) (98:D4) [11:31:44:390]: Machine policy value 'Debug' is 0
MSI (c) (98:D4) [11:31:44:390]: ******* RunEngine:
******* Product: http://<SANITIZED-FOR-PRIVACY>/BadURL/package.msi
******* Action:
******* CommandLine: **********
MSI (c) (98:D4) [11:31:44:390]: File path is a URL. Downloading file. . .
MSI (c) (98:D4) [11:31:44:437]: MSI WinHttp: Proxy Settings Proxy: (none) | Bypass: (none) | AccessType: 0
MSI (c) (98:D4) [11:31:44:453]: Download of URL resource http://<SANITIZED-FOR-PRIVACY>/BadURL/package.msi failed with last error 2
MSI (c) (98:D4) [11:31:44:453]: MainEngineThread is returning 2
=== Verbose logging stopped: 4/2/2010 11:31:44 ===
The message from WI is somewhat confusing to the average user - he/she may not realize (and shouldn't need to) that the boostrapper is part of an online / web install that requires additional resources. The message from WI gives the impression that the "setup.exe" file itself is somehow corrupt or incomplete.
Is it possible for the bootstrapper to validate the existence of the online MSI before invoking msiexec.exe? If the bootstrapper detects that the MSI cannot be found, it could present an error message with better wording and then it should not invoke msiexec.exe.
thanks for you help,
-Todd
FOLLOW US
Get the latest news in Application Packaging