However, in this case installation is fine.
Only upgrades are affected, and even upgrades complete (seemingly) successfully.
There are no other burn processes spawned as suggested in the linked issue (ID:
3538260).
In the case I have described it seems as if 'ScheduleReboot' simply causes burn
to skip detection of dependencies during the bundle uninstall (related upgrade).
i.e. The following lines are "missing" from the package plan if an msi in the
bundle includes a scheduled reboot:
[0374:0BE4][2012-07-12T15:03:20]: Will not uninstall package: Package P3, found
dependents: 1
[0374:0BE4][2012-07-12T15:03:20]: Found dependent:
{a0bd2275-4768-4a8f-8590-1ec812cddf7a}, name: Bundle B2
[0374:0BE4][2012-07-12T15:03:20]: Plan Package Begin...
[0374:0BE4][2012-07-12T15:03:20]: Will not uninstall package: Package P2, found
dependents: 1
[0374:0BE4][2012-07-12T15:03:20]: Found dependent:
{a0bd2275-4768-4a8f-8590-1ec812cddf7a}, name: Bundle B2
and so they are uninstalled (incorrectly).
Sounds like it could be related to:
http://sourceforge.net/tracker/?func=detail&aid=3538260&group_id=105970&atid=642714
From: timcomp...@hotmail.com
To: wix-users@lists.sourceforge.net
Subject: RE: Bootstrapper Upgrade Issue
Date: Thu, 12 Jul 2012 15:38:45 +1000
Further investigation (trial and error) reveals that this has something to do
with 'ScheduleReboot'.
It seems that if any of the packages schedule a reboot using:
<InstallExecuteSequence>
<ScheduleReboot After="InstallFinalize"/>
</InstallExecuteSequence>
it causes the issue described.
However, if no reboot is scheduled by any package (I manually removed it for
testing) then upgrading works as expected.
Any ideas?
From: timcomp...@hotmail.com
To: wix-users@lists.sourceforge.net
Subject: Bootstrapper Upgrade Issue
Date: Thu, 12 Jul 2012 15:31:39 +1000
I am using WiX 3.6.3102, and I'm having an issue when upgrading my burn
bootstrapper.
For testing upgrade scenario's I have built two bundle's:
Bundle B1 v1.0.1.0
- Package P1 vX.X.X.X
- Package P2 vY.Y.Y.Y
- Package P3 v1.0.1.0
Bundle B2 v1.0.2.0
- Package P1 vX.X.X.X
- Package P2 vY.Y.Y.Y
- Package P3 v1.0.2.0
As you can see only 1 msi package is being upgraded (MajorUpgrade), and the
bundle version also changes accordingly.
Installing B1 goes without a hitch.
When I am installing B2 in order to upgrade B1, the installation appears to
complete successfully, however I am left with:
B2 v1.0.2.0 installed
Package P3 v1.0.2.0 installed
Packages P1 and P2 have dissappeared (uninstalled during the upgrade process).
If I then perform a repair on B2 it reinstalls P1 and P2 and everything is
correct.
Can you help me? What is meant to happen in this scenario (see below)?
See relevant logs from upgrade below (names & directories have been modified):
...
[05BC:0134][2012-07-12T13:39:47]: Detected package: Netfx4Full, state: Present,
cached: None
[05BC:0134][2012-07-12T13:39:47]: Detected package: Package P1, state: Present,
cached: Complete
[05BC:0134][2012-07-12T13:39:47]: Detected package: Package P2, state: Present,
cached: Complete
[05BC:0134][2012-07-12T13:39:47]: Detected package: Package P3, state: Absent,
cached: None
...
[01CC:02B0][2012-07-12T13:40:00]:
Caching bundle from: 'C:\Bundle B2 1.0.2.0.exe' to: 'C:\Documents and
Settings\All Users\Application Data\Package
Cache\{fc4df719-81bf-4351-b74a-e500ebea2bc6}\Bundle B2 1.0.2.0.exe'
[01CC:02B0][2012-07-12T13:40:00]:
Registering bundle dependency provider:
{fc4df719-81bf-4351-b74a-e500ebea2bc6}, version: 1.0.2.0
[01CC:0374][2012-07-12T13:40:05]:
Verified acquired payload: Package P3 at path: C:\Documents and
Settings\All Users\Application Data\Package Cache\.unverified\Package
P3, moving to: C:\Documents and Settings\All Users\Application
Data\Package
Cache\{8E8091BD-64F6-480B-8A7D-EAB4801EA750}v1.0.2.0\Package P3
1.0.2.0.msi.
[01CC:02B0][2012-07-12T13:40:05]: Registering
dependency: {fc4df719-81bf-4351-b74a-e500ebea2bc6} on package provider:
{6E508F02-4E37-4DB3-8918-B9D2B0D8D796}, package: Package P1
[01CC:02B0][2012-07-12T13:40:05]:
Registering dependency: {fc4df719-81bf-4351-b74a-e500ebea2bc6} on
package provider: {AE821785-FE11-4925-860A-0EA69DCA22D1}, package:
Package P2
[01CC:02B0][2012-07-12T13:40:05]: Applying execute
package: Softec, action: Install, path: C:\Documents and Settings\All
Users\Application Data\Package
Cache\{8E8091BD-64F6-480B-8A7D-EAB4801EA750}v1.0.2.0\Package P3
1.0.2.0.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[01CC:02B0][2012-07-12T13:40:14]:
Registering package dependency provider:
{8E8091BD-64F6-480B-8A7D-EAB4801EA750}, version: 1.0.2.0, package:
Package P3
[05BC:0134][2012-07-12T13:40:14]: Applied execute package: Package P3, result:
0x0, restart: Required
[01CC:02B0][2012-07-12T13:40:14]:
Registering dependency: {fc4df719-81bf-4351-b74a-e500ebea2bc6} on
package provider: {8E8091BD-64F6-480B-8A7D-EAB4801EA750}, package:
Package P3
[01CC:02B0][2012-07-12T13:40:36]: Applying execute
package: {531cb5a9-e18d-4dbd-8afb-6c690ebaeb30}, action: Uninstall,
path: C:\Documents and Settings\All Users\Application Data\Package
Cache\{531cb5a9-e18d-4dbd-8afb-6c690ebaeb30}\Bundle B1 1.0.1.0.exe,
arguments: '"C:\Documents and Settings\All Users\Application
Data\Package Cache\{531cb5a9-e18d-4dbd-8afb-6c690ebaeb30}\Bundle B1
1.0.1.0.exe" -uninstall -quiet -burn.related.upgrade'
[05BC:07E0][2012-07-12T13:41:38]: Received system request to shut down the
process: critical: No, elevated: No, allowed: No
[01CC:02B0][2012-07-12T13:41:39]:
Removed package dependency provider:
{531cb5a9-e18d-4dbd-8afb-6c690ebaeb30}, package:
{531cb5a9-e18d-4dbd-8afb-6c690ebaeb30}
[05BC:0134][2012-07-12T13:41:39]: Applied execute package:
{531cb5a9-e18d-4dbd-8afb-6c690ebaeb30}, result: 0x0, restart: None
[05BC:0134][2012-07-12T13:41:39]: Apply complete, result: 0x0, restart:
Required, ba requested restart: Yes
...
As
you can see Bundle B1 is told to uninstall (Bundle B1 1.0.1.0.exe"
-uninstall -quiet -burn.related.upgrade') at the end of the apply
sequence, and it does as it's told, including uninstalling P1 and P2.
Here are relevant parts of that log:
[02D4:0370][2012-07-12T13:40:36]:
Burn v3.6.3102.0, Windows v5.1 (Build 2600: Service Pack 3), path:
C:\Documents and Settings\All Users\Application Data\Package
Cache\{531cb5a9-e18d-4dbd-8afb-6c690ebaeb30}\Bundle B1 1.0.1.0.exe,
cmdline: '-uninstall -quiet -burn.related.upgrade -burn.embedded
BurnPipe.{80887755-ADB6-4CCD-966B-5EFFB613BC3F}
{6ACD5DB8-511C-4A28-9648-89CD9BF7F6A4} 460'
...
[02D4:0370][2012-07-12T13:40:38]:
Detected related package: {58821A6D-9031-44C1-9783-C5B9874BD5E8},
scope: PerMachine, version: 1.0.17692.0, language: 0 operation:
Downgrade
[02D4:0370][2012-07-12T13:40:38]: Detected package: Netfx4Full, state: Present,
cached: None
[02D4:0370][2012-07-12T13:40:38]: Detected package: Package P1, state: Present,
cached: Complete
[02D4:0370][2012-07-12T13:40:38]: Detected package: Package P2, state: Present,
cached: Complete
[02D4:0370][2012-07-12T13:40:38]: Detected package: Package P3, state:
Obsolete, cached: Complete
...
[02D4:0370][2012-07-12T13:40:38]:
Planned related bundle: {fc4df719-81bf-4351-b74a-e500ebea2bc6}, type:
Upgrade, default requested: None, ba requested: None, execute: None,
rollback: None, dependency: None
[02D4:0370][2012-07-12T13:40:38]:
Planned package: Package P3, state: Obsolete, default requested: None,
ba requested: None, execute: None, rollback: None, cache: No, uncache:
Yes, dependency: Unregister
[02D4:0370][2012-07-12T13:40:38]: Planned
package: Package P2, state: Present, default requested: Absent, ba
requested: Absent, execute: Uninstall, rollback: Install, cache: No,
uncache: Yes, dependency: Unregister
[02D4:0370][2012-07-12T13:40:38]:
Planned package: Package P1, state: Present, default requested: Absent,
ba requested: Absent, execute: Uninstall, rollback: Install, cache: No,
uncache: Yes, dependency: Unregister
[02D4:0370][2012-07-12T13:40:38]:
Planned package: Netfx4Full, state: Present, default requested: None,
ba requested: None, execute: None, rollback: None, cache: No, uncache:
No, dependency: None
...
[0768:0498][2012-07-12T13:40:42]:
Applying execute package: Package P2, action: Uninstall, path:
C:\Documents and Settings\All Users\Application Data\Package
Cache\{AE821785-FE11-4925-860A-0EA69DCA22D1}vY.Y.Y.Y\Package P2
Y.Y.Y.Y.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0768:0498][2012-07-12T13:40:44]:
Removed package dependency provider:
{AE821785-FE11-4925-860A-0EA69DCA22D1}, package: Package P2
[02D4:0370][2012-07-12T13:40:44]: Applied execute package: Package P2, result:
0x0, restart: None
[0768:0498][2012-07-12T13:40:44]:
Applying execute package: Package P1, action: Uninstall, path:
C:\Documents and Settings\All Users\Application Data\Package
Cache\{6E508F02-4E37-4DB3-8918-B9D2B0D8D796}vX.X.X.X\Package P1
X.X.X.X.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0768:0498][2012-07-12T13:41:37]:
Removed package dependency provider:
{6E508F02-4E37-4DB3-8918-B9D2B0D8D796}, package: Package P1
[02D4:0370][2012-07-12T13:41:37]: Applied execute package: Package P1, result:
0x0, restart: Required
...
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
