Hello,
We're using Advanced Installer 23.9, per-machine MSI with EXE bootstrapper.
In our product install we have a custom feature selection dialog to let the user
select some features to be installed. There are a few checkboxes on this dialog,
and each of these corresponds to one property, which is set to true when that
particular feature is selected. On the Organization page, each optional feature
has "Not installed" as the default with an "Installed if" condition, for example
CHECKBOX_RL = "true".
This works fine on a direct installation. For one particular feature, say
Feature RL, there is a corresponding Windows service to be installed and
started, and even that works correctly when Feature RL is selected. Because this
feature is large, its payload is downloaded at install time, and the download is
conditioned on the same property.
The problem appears on upgrade. Version 3.1.0 is already installed, and we then
install 3.1.4 without uninstalling, leaving Feature RL unticked exactly as in the
working direct-install case. The feature gets selected anyway, so its service is
created and started, while the downloaded part of the feature is missing — those
downloads are conditioned on the property, which is correctly false. The service
cannot start, we get Error 1920, and since it is marked vital the whole upgrade
rolls back.
From the verbose log, CHECKBOX_RL is never set, so the feature condition is
correctly false, yet the feature is selected anyway:
15:39:59 MigrateFeatureStates: ... setting feature 'FeatureRL' to 'Absent'
15:40:06 PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'ALL'
15:40:09 UpdateFeaturesInstallStates ... Return value 1
15:40:09 Doing action: FeatureSelectionDlg
15:40:14 Feature: FeatureRL; Installed: Absent; Request: Local; Action: Local
Looks like MigrateFeatureStates runs only on upgrade.
Not sure what exactly is going wrong. Please let us know the reasons and a solution.
Thanks in advance,
SDutt
FOLLOW US
Get the latest news in Application Packaging