Bundle Upgrade with AddOn Repair Failure

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Bundle Upgrade with AddOn Repair Failure

rw1017
This post has NOT been accepted by the mailing list yet.
All,
I'm just checking to see if someone might be able to confirm if this scenario is a bug or not.  If it is, i'll enter it in.  I'm currently using Release Wix 3.9.1006.0

We have 4 Bundles(1 Main bundle, and 2 Related AddOn bundles).

Most of all cases are smooth except for one.
We are upgrading the Main Bundle that has a generated GUID of:
{9faf056f-c78f-4548-8336-698c3ce1ae22}

and 2 AddOn's with generated GUIDs of:
{3dd1ca61-290b-4f47-8035-da8795b27740}
{f7418efa-d7e7-42da-be5f-c1ed2f5c3181}

When upgrading the Main Bundle, I'd guess that it would:
1. Add registration for New Main Bundle
2. Upgrade/Install Packages
3. Repair 2 AddOn's
4. Remove Registraion of Old Main Bundle

The actual outcome that is happening in this case is:
1. Add registration for New Main Bundle
2. Upgrade/Install Packages
3. Repairs 1 Addon
4. Remove Registration of Old Main Bundle, which in turn Uninstalls Other Addon.
5. Attempts to Repair the Addon, but fails because it's already removed from #4.

Here are excerpts from the Log of what is happening(I needed to delete exe names):

[2B24:24D4][2017-05-16T14:38:36]i102: Detected related bundle: {3dd1ca61-290b-4f47-8035-da8795b27740}, type: Addon, scope: PerMachine, version: 1.7.25804.0, operation: Install
[2B24:24D4][2017-05-16T14:38:36]i102: Detected related bundle: {9faf056f-c78f-4548-8336-698c3ce1ae22}, type: Upgrade, scope: PerMachine, version: 1.7.25804.0, operation: MajorUpgrade
[2B24:24D4][2017-05-16T14:38:36]i102: Detected related bundle: {f7418efa-d7e7-42da-be5f-c1ed2f5c3181}, type: Addon, scope: PerMachine, version: 1.7.25804.0, operation: Install
.
.
.

[2B24:24D4][2017-05-16T14:38:36]i207: Planned related bundle: {3dd1ca61-290b-4f47-8035-da8795b27740}, type: Addon, default requested: Present, ba requested: Present, execute: Install, rollback: None, dependency: Register
[2B24:24D4][2017-05-16T14:38:36]i207: Planned related bundle: {9faf056f-c78f-4548-8336-698c3ce1ae22}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None
[2B24:24D4][2017-05-16T14:38:36]i207: Planned related bundle: {f7418efa-d7e7-42da-be5f-c1ed2f5c3181}, type: Addon, default requested: Present, ba requested: Present, execute: Install, rollback: None, dependency: Register
.
.
.
[3610:1B18][2017-05-16T14:38:37]i320: Registering bundle dependency provider: {fdcbbec4-7fb7-489a-9c0e-f96b7f8ba0ae}, version: 1.8.2594.3
.
.
.
[3610:1B18][2017-05-16T14:56:34]i301: Applying execute package: {3dd1ca61-290b-4f47-8035-da8795b27740}, action: Install, path: C:\ProgramData\Package Cache\{3dd1ca61-290b-4f47-8035-da8795b27740}\[DELETED.exe], arguments: '"C:\ProgramData\Package Cache\{3dd1ca61-290b-4f47-8035-da8795b27740}\[DELETED.exe]" -quiet -burn.related.addon -burn.ignoredependencies={fdcbbec4-7fb7-489a-9c0e-f96b7f8ba0ae} -burn.ancestors={fdcbbec4-7fb7-489a-9c0e-f96b7f8ba0ae}'
[2B24:24D4][2017-05-16T14:56:35]i319: Applied execute package: {3dd1ca61-290b-4f47-8035-da8795b27740}, result: 0x0, restart: None
[3610:1B18][2017-05-16T14:56:35]i325: Registering dependency: {fdcbbec4-7fb7-489a-9c0e-f96b7f8ba0ae} on package provider: {3dd1ca61-290b-4f47-8035-da8795b27740}, package: {3dd1ca61-290b-4f47-8035-da8795b27740}
[3610:1B18][2017-05-16T14:56:35]i301: Applying execute package: {9faf056f-c78f-4548-8336-698c3ce1ae22}, action: Uninstall, path: C:\ProgramData\Package Cache\{9faf056f-c78f-4548-8336-698c3ce1ae22}\[DELETED.exe], arguments: '"C:\ProgramData\Package Cache\{9faf056f-c78f-4548-8336-698c3ce1ae22}\[DELETED.exe]" -uninstall -quiet -burn.related.upgrade -burn.ancestors={fdcbbec4-7fb7-489a-9c0e-f96b7f8ba0ae}'
[2B24:24D4][2017-05-16T14:56:47]i319: Applied execute package: {9faf056f-c78f-4548-8336-698c3ce1ae22}, result: 0x0, restart: None
[3610:1B18][2017-05-16T14:56:47]i301: Applying execute package: {f7418efa-d7e7-42da-be5f-c1ed2f5c3181}, action: Install, path: C:\ProgramData\Package Cache\{f7418efa-d7e7-42da-be5f-c1ed2f5c3181}\[DELETED.exe], arguments: '"C:\ProgramData\Package Cache\{f7418efa-d7e7-42da-be5f-c1ed2f5c3181}\[DELETED.exe]" -quiet -burn.related.addon -burn.ignoredependencies={fdcbbec4-7fb7-489a-9c0e-f96b7f8ba0ae} -burn.ancestors={fdcbbec4-7fb7-489a-9c0e-f96b7f8ba0ae}'
[3610:1B18][2017-05-16T14:56:47]e000: Error 0x80070003: Failed to create embedded process atpath: C:\ProgramData\Package Cache\{f7418efa-d7e7-42da-be5f-c1ed2f5c3181}\[DELETED.exe]
[3610:1B18][2017-05-16T14:56:47]e000: Error 0x80070003: Failed to run bundle as embedded from path: C:\ProgramData\Package Cache\{f7418efa-d7e7-42da-be5f-c1ed2f5c3181}\[DELETED.exe]
[3610:1B18][2017-05-16T14:56:47]e000: Error 0x80070003: Failed to execute EXE package.
[2B24:24D4][2017-05-16T14:56:47]e000: Error 0x80070003: Failed to configure per-machine EXE package.
[2B24:24D4][2017-05-16T14:56:47]w350: Applied non-vital package: {f7418efa-d7e7-42da-be5f-c1ed2f5c3181}, encountered error: 0x80070003. Continuing...
[3610:1B18][2017-05-16T14:56:47]i325: Registering dependency: {fdcbbec4-7fb7-489a-9c0e-f96b7f8ba0ae} on package provider: {f7418efa-d7e7-42da-be5f-c1ed2f5c3181}, package: {f7418efa-d7e7-42da-be5f-c1ed2f5c3181}
[2B24:24D4][2017-05-16T14:56:47]i399: Apply complete, result: 0x0, restart: Required, ba requested restart:  No


My Guess is that when Burn Queries for Related Bundles, it does it in order of the Registry(alphabetical) on the GUIDs it detects.

Is this the intended behavior or a bug in burn?

Thanks!
Richard