I have a strange behaviour with my installscript MSI projects.
I have an installer for a version 2.0.0, a version 2.0.1 and a version 2.0.2. As there are not many changes involved, except some newer versions of files, it should be a simple product update.
2.0.0 -> 2.0.1: OK 2.0.1 -> 2.0.2: OK
2.0.0 -> 2.0.2: update works without any problem (or at least no errors are reported), but when starting the application, it reinstalls version 2.0.0!
I had a look into the windows event viewer, I have the following entry:
Detection of product '{4D2B...}', feature 'myapp' failed during request for component '{634B...}'.
The component 634B... is in fact the main exe file of the application I am installing...
What am I doing wrong?
Why does the update 2.0.0 -> 2.0.1 and 2.0.1 -> 2.0.2 work, but not 2.0.0 -> 2.0.2?
I tried to get the logs of the updates and had a look at the SELMGR lines:
2.0.0 -> 2.0.1: not any single SELMGR line entry MSI (s) (38:80) [16:06:15:156]: Machine policy value 'EnforceUpgradeComponentRules' is 0
2.0.1 -> 2.0.2: following SELMGR lines: MSI (s) (38:84) [16:08:46:797]: Machine policy value 'EnforceUpgradeComponentRules' is 0 MSI (s) (38:84) [16:08:46:797]: SELMGR: New components have been added to feature 'myapp' MSI (s) (38:84) [16:08:46:797]: SELMGR: Component '_759D251A379501D5B169D0C0C55B792F' is a new component added to feature 'myapp'
and upgrade worked in both cases.
Now, for 2.0.0 -> 2.0.2: MSI (s) (60:0C) [15:46:28:860]: Machine policy value 'EnforceUpgradeComponentRules' is 0 MSI (s) (60:0C) [15:46:28:860]: SELMGR: Component 'upgradeDB.sql_SQLComponent' is registered to feature 'myapp', but is not present in the FeatureComponents table. Removal of components from a feature is not supported! MSI (s) (60:0C) [15:46:28:860]: SELMGR: Removal of a component from a feature is not supported
How does it come that a component is "removed" between 2.0.0 and 2.0.2, but neither 2.0.0-2.0.1 nor 2.0.1-2.0.2 are reporting it?
