This log is telling you that you have the product
{B92051A3-3ABB-4A26-A615-2298BE7CBC28} already installed, so by definition this
is NOT a major upgrade (maybe your bootstrapper doesn't property process
non-major upgrades?).
If you expected this to be a major upgrade, then you need to find out how your
component MSI with package code {AA2C487B-BA31-44D6-83A3-DFF84381C6E3} got the
same ProductCode as the product identified as "Product Name: xxx xxx Manager.
Product Version: 4.0.0.53726. Product Language: 1033. Manufacturer: xxx
Systems, Inc.". It was NOT the same MSI used to install that ProductCode
originally.
Major upgrades NEVER share the same ProductCode with anything else. Instead
they share UpgradeCode. Sharing ProductCode is the definition of "minor
upgrades" and "small updates".
-Blair
> Date: Mon, 11 Nov 2013 20:49:18 -0800
> From: [email protected]
> To: [email protected]
> Subject: [WiX-users] Strange and interesting problem with major upgrades
>
> Hello All,
>
> I am running into a strange issue with a major upgrade of an installer.
> I have a bootstrapper which has around 5 .msi packages embedded inside.
> The bootstrapper is a VC++ .exe with the requested execution level being
> set to "AsInvoker".
>
> Let me explain my problem.
>
> - I have "AlwaysInstallElevated" policy enabled at both the machine level
> and user level.
> -The server has UAC enabled.
> -I create a user(non admin) and make him part of the "Remote Desktop Users"
> group.
> - I log in as this standard user and install v1.0 of our product( i.e i
> execute v1.0 of the bootstrapper exe)
> Everything works fine.
> -I upgrade to v1.1 again using the bootstrapper and everything works fine.
> -I attempt an upgrade to v1.1.1 using the bootstrapper and the upgrade
> fails.
>
> Upon further investigation, it comes to my notice that one of the component
> installers within the bootstrapper fails to upgrade with the following lines
> of error in the .msi log file:
>
> PROPERTY CHANGE: Adding PackageCode property. Its value is
> '{AA2C487B-BA31-44D6-83A3-DFF84381C6E3}'.
> MSI (s) (58:74) [07:26:14:994]: Product Code passed to Engine.Initialize:
>
> '{B92051A3-3ABB-4A26-A615-2298BE7CBC28}'
> MSI (s) (58:74) [07:26:14:994]: Product Code from property table before
> transforms: '{B92051A3-3ABB-4A26-A615-2298BE7CBC28}'
> MSI (s) (58:74) [07:26:14:994]: Product Code from property table after
> transforms: '{B92051A3-3ABB-4A26-A615-2298BE7CBC28}'
> MSI (s) (58:74) [07:26:14:994]: *Product registered: entering maintenance
> mode*
> MSI (s) (58:74) [07:26:14:994]: Determined that existing product (either
> this product or the product being upgraded with a patch) is installed
> per-machine.
> MSI (s) (58:74) [07:26:14:995]: PROPERTY CHANGE: Adding ALLUSERS property.
> Its value is '1'.
> MSI (s) (58:74) [07:26:14:995]: Product
> {B92051A3-3ABB-4A26-A615-2298BE7CBC28} is admin assigned: LocalSystem owns
> the publish key.
> MSI (s) (58:74) [07:26:14:995]: Product
> {B92051A3-3ABB-4A26-A615-2298BE7CBC28} is managed.
> MSI (s) (58:74) [07:26:14:995]: Machine policy value 'AlwaysInstallElevated'
> is 1
> MSI (s) (58:74) [07:26:14:995]: User policy value 'AlwaysInstallElevated' is
> 1
> MSI (s) (58:74) [07:26:14:995]: MSI_LUA: No credentials required as all
> installs will run elevated due to AlwaysInstallElevated policy setting
> MSI (s) (58:74) [07:26:14:995]: PROPERTY CHANGE: Adding ProductState
> property. Its value is '5'.
> MSI (s) (58:74) [07:26:14:996]: PROPERTY CHANGE: Adding
> ProductToBeRegistered property. Its value is '1'.
> MSI (s) (58:74) [07:26:14:997]: Entering
> CMsiConfigurationManager::SetLastUsedSource.
> MSI (s) (58:74) [07:26:14:998]: Specifed source is not already in a list.
> MSI (s) (58:74) [07:26:14:998]: User policy value 'SearchOrder' is 'nmu'
> MSI (s) (58:74) [07:26:14:998]: Machine policy value 'DisableBrowse' is 0
> MSI (s) (58:74) [07:26:14:998]: Machine policy value 'AllowLockdownBrowse'
> is 0
> MSI (s) (58:74) [07:26:14:998]: Machine policy value 'AlwaysInstallElevated'
> is 1
> MSI (s) (58:74) [07:26:14:999]: User policy value 'AlwaysInstallElevated' is
> 1
> MSI (s) (58:74) [07:26:14:999]: Product
> {B92051A3-3ABB-4A26-A615-2298BE7CBC28} is admin assigned: LocalSystem owns
> the publish key.
> MSI (s) (58:74) [07:26:14:999]: Product
> {B92051A3-3ABB-4A26-A615-2298BE7CBC28} is managed.
> MSI (s) (58:74) [07:26:14:999]: Running product
> '{B92051A3-3ABB-4A26-A615-2298BE7CBC28}' with elevated privileges: Product
> is assigned.
> MSI (s) (58:74) [07:26:14:999]: Adding new sources is not allowed.
> MSI (s) (58:74) [07:26:14:999]: Warning: rejected attempt to add new source
> 'C:\Users\kiran\AppData\Local\Temp\Ctx-DD816FE4-2DEE-43B9-8C75-B684400B36DE\Extract\'
> (product: {B92051A3-3ABB-4A26-A615-2298BE7CBC28})
> MSI (s) (58:74) [07:26:15:000]: MSI_LUA: Elevation prompt disabled for
> silent installs
> MSI (s) (58:74) [07:26:15:000]: Note: 1: 1729
> MSI (s) (58:74) [07:26:15:000]: Product: xxx xxx Manager -- Configuration
> failed.
>
> MSI (s) (58:74) [07:26:15:001]: Windows Installer reconfigured the product.
> Product Name: xxx xxx Manager. Product Version: 4.0.0.53726. Product
> Language: 1033. Manufacturer: xxx Systems, Inc.. Reconfiguration success or
> error status: 1625.
>
> MSI (s) (58:74) [07:26:15:002]: MainEngineThread is returning 1625
> MSI (s) (58:E0) [07:26:15:002]: No System Restore sequence number for this
> installation.
> *This installation is forbidden by system policy. Contact your system
> administrator.*
>
> The installer is configured for major upgrade with the "Upgrade" table
> entries populated.
> The installer is the same in both v1.1 and v1.1.1 of the bootstrapper.
>
> I see that the installer enters maintanance mode which should not be the
> case given the fact that the upgrade table has been configured properly.
>
> I also have one more observation:
> If i happen to launch the bootstrapper from an elevated command prompt, then
> i dont hit this problem.
> Instead the installer runs and then exits gracefully stating that the
> version of the product is already installed. The message is from a custom
> action.
>
> I am at loss to understand what could be wrong.
>
> Any help would be very much appreciated.
>
> Thanks,
> Kiran Hegde
>
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Strange-and-interesting-problem-with-major-upgrades-tp7590575.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
