Discussion:
[WiX-users] Burn: Really weird upgrade problem.
Miss Parker
13 years ago
Permalink
Hi all!

I have a really strange upgrade problem that I could use some help with.
Please. :)

I've implemented my own bootstrapper application, but when I started this
project I made a simple BA (that was based on WixBA) just for testing. When
I use my test BA, I can upgrade without any problems at all, but when I use
my real BA the upgrade fails. The bundles are identical in both BA's, and
are using the latest BootstrapperCore.dll

This is the scenario (that fails....):

I install my real BA, version 1.0.0.0 with 3 msi's.
I change the version to 2.0.0.0, updates one of the msi's and rebuilds.
I run the installation, and it's recognized as an upgrade and the upgrade
(Brand) is installed. The problem occures when the bundle tries to update
itself. The BA then decides that one of the other msi's, Fido.msi, (NOT
updated) should be uninstalled.

Since the upgrade works with my test BA I'm guessing this is not a Burn bug,
but something I'm doing wrong. Does anyone have any idea what makes Burn
react this way? I can of course see in the log that it has something to do
with the lack of dependants, but I don't understand why Fido isn't dependent
on the new bundle.

The upgrade log

[170C:1710][2012-09-10T13:43:56]: Burn v3.6.3303.0, Windows v5.1 (Build
2600: Service Pack 3), path: C:\Documents and Settings\All Users\Application
Data\Package Cache\{da00e8c3-6096-4698-8f02-18008bcf907d}\Installer.exe,
cmdline: '-uninstall -quiet -burn.related.upgrade -burn.embedded
BurnPipe.{D8212B90-93BB-4F74-95C3-E7231A5A1FEF}
{E24F96C7-218C-42E5-945D-6FED133F0C76} 5184'
[170C:1710][2012-09-10T13:43:56]: This bundle is being run by a related
bundle as type 'Upgrade'.
[170C:1710][2012-09-10T13:43:56]: Initializing string variable 'IDVAR' to
value 'default'
[170C:1710][2012-09-10T13:43:56]: Setting string variable 'WixBundleLog' to
value 'C:\DOCUME~1\v0c8665\LOCALS~1\Temp\Installer_20120910134356.log'
[170C:1710][2012-09-10T13:43:57]: Loading managed bootstrapper application.
[170C:1710][2012-09-10T13:43:57]: Creating BA thread to run asynchronously.
[170C:1768][2012-09-10T13:43:58]: SilentInstallmanager constructor
[170C:1768][2012-09-10T13:43:58]: Setting string variable 'IDVAR' to value
'124017'
[170C:1710][2012-09-10T13:43:58]: Detect 4 packages
[170C:1710][2012-09-10T13:43:58]: Setting string variable
'Netfx35x64FullVersion' to value '3.5.30729.01'
[170C:1710][2012-09-10T13:43:58]: Setting string variable
'Netfx35FullVersion' to value '3.5.30729.01'
[170C:1710][2012-09-10T13:43:58]: Setting string variable
'Netfx4x64FullVersion' to value '4.0.30319'
[170C:1710][2012-09-10T13:43:58]: Setting string variable
'Netfx4FullVersion' to value '4.0.30319'
[170C:1710][2012-09-10T13:43:58]: Detected related bundle:
{c7b317c5-8468-4316-be7f-044b329ffcd8}, type: Upgrade, scope: PerMachine,
version: 1.1.0.0, operation: None
[170C:1710][2012-09-10T13:43:58]: Condition 'Netfx4FullVersion AND (NOT
VersionNT64 OR Netfx4x64FullVersion)' evaluates to true.
[170C:1710][2012-09-10T13:43:58]: Detected related package:
{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version: 2.1.0.0,
language: 0 operation: MajorUpgrade
[170C:1710][2012-09-10T13:43:58]: Detected related package:
{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version: 2.1.0.0,
language: 0 operation: Downgrade
[170C:1710][2012-09-10T13:43:58]: Detected package: Netfx4Full, state:
Present, cached: None
[170C:1710][2012-09-10T13:43:58]: Detected package: Fido, state: Present,
cached: Complete
[170C:1710][2012-09-10T13:43:58]: Detected package: ClientUpdate, state:
Present, cached: Complete
[170C:1710][2012-09-10T13:43:58]: Detected package: Brand, state: Obsolete,
cached: Complete
[170C:1710][2012-09-10T13:43:58]: DetectComplete Silent install
[170C:1710][2012-09-10T13:43:58]: Detect complete, result: 0x0
[170C:1710][2012-09-10T13:43:58]: Plan 4 packages, action: Uninstall
[170C:1710][2012-09-10T13:43:58]: PlanPackageBeginEventArgs Silent install
pack id:Brand, State: None
[170C:1710][2012-09-10T13:43:58]: PlanPackageBeginEventArgs Silent install
pack id:ClientUpdate, State: Absent
[170C:1710][2012-09-10T13:43:58]: Will not uninstall package: ClientUpdate,
found dependents: 1
[170C:1710][2012-09-10T13:43:58]: Found dependent:
{c7b317c5-8468-4316-be7f-044b329ffcd8}, name: Installer
[170C:1710][2012-09-10T13:43:58]: PlanPackageBeginEventArgs Silent install
pack id:Fido, State: Absent
[170C:1710][2012-09-10T13:43:58]: Setting string variable
'WixBundleRollbackLog_Fido' to value
'C:\DOCUME~1\v0c8665\LOCALS~1\Temp\Installer_20120910134356_0_Fido_rollback.log'
[170C:1710][2012-09-10T13:43:58]: Setting string variable
'WixBundleLog_Fido' to value
'C:\DOCUME~1\v0c8665\LOCALS~1\Temp\Installer_20120910134356_0_Fido.log'
[170C:1710][2012-09-10T13:43:58]: PlanPackageBeginEventArgs Silent install
pack id:Netfx4Full, State: None
[170C:1710][2012-09-10T13:43:58]: Skipping dependency registration on
package with no dependency providers: Netfx4Full
[170C:1710][2012-09-10T13:43:58]: Planned related bundle:
{c7b317c5-8468-4316-be7f-044b329ffcd8}, type: Upgrade, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None
[170C:1710][2012-09-10T13:43:58]: Planned package: Brand, state: Obsolete,
default requested: None, ba requested: None, execute: None, rollback: None,
cache: No, uncache: Yes, dependency: Unregister
[170C:1710][2012-09-10T13:43:58]: Planned package: ClientUpdate, state:
Present, default requested: Absent, ba requested: Absent, execute: None,
rollback: None, cache: No, uncache: No, dependency: Unregister
[170C:1710][2012-09-10T13:43:58]: Planned package: Fido, state: Present,
default requested: Absent, ba requested: Absent, execute: Uninstall,
rollback: Install, cache: No, uncache: Yes, dependency: Unregister
[170C:1710][2012-09-10T13:43:58]: Planned package: Netfx4Full, state:
Present, default requested: None, ba requested: None, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[170C:1710][2012-09-10T13:43:58]: PlanComplete Silent install
[170C:1710][2012-09-10T13:43:58]: Plan complete, result: 0x0
[170C:1710][2012-09-10T13:43:58]: Apply begin
[13D0:13D4][2012-09-10T13:43:59]: Creating a system restore point.
[13D0:13D4][2012-09-10T13:43:59]: Could not create system restore point,
error: 0x80070422. Continuing...
[13D0:13D4][2012-09-10T13:43:59]: Removed dependency:
{da00e8c3-6096-4698-8f02-18008bcf907d} on package provider:
{EB1F3B6E-E005-451C-BAC6-BAE3B4054547}, package Brand
[13D0:13D4][2012-09-10T13:43:59]: Removed dependency:
{da00e8c3-6096-4698-8f02-18008bcf907d} on package provider:
{083FAB46-0302-4172-8910-07B9A5CF8959}, package ClientUpdate
[13D0:13D4][2012-09-10T13:43:59]: Removed dependency:
{da00e8c3-6096-4698-8f02-18008bcf907d} on package provider:
{7B5DA339-D6FC-4031-870C-1E4CE9C92361}, package Fido
[13D0:13D4][2012-09-10T13:43:59]: Applying execute package: Fido, action:
Uninstall, path: C:\Documents and Settings\All Users\Application
Data\Package Cache\{7B5DA339-D6FC-4031-870C-1E4CE9C92361}v1.0.33\FIDO.msi,
arguments: ' MSIFASTINSTALL="7"'
[13D0:13D4][2012-09-10T13:44:14]: Error 0x80070643: Failed to uninstall MSI
package.
[13D0:13D4][2012-09-10T13:44:14]: Error 0x80070643: Failed to execute MSI
package.
[170C:1710][2012-09-10T13:44:14]: Error 0x80070643: Failed to configure
per-machine MSI package.
[170C:1710][2012-09-10T13:44:14]: Applied execute package: Fido, result:
0x80070643, restart: None
[170C:1710][2012-09-10T13:44:14]: Error 0x80070643: Failed to execute MSI
package.
[13D0:13D4][2012-09-10T13:44:14]: Skipped rollback of package: Fido, action:
Install, already: Present
[170C:1710][2012-09-10T13:44:14]: Applied rollback package: Fido, result:
0x0, restart: None
[13D0:13D4][2012-09-10T13:44:14]: Registering dependency:
{da00e8c3-6096-4698-8f02-18008bcf907d} on package provider:
{7B5DA339-D6FC-4031-870C-1E4CE9C92361}, package: Fido
[13D0:13D4][2012-09-10T13:44:14]: Registering dependency:
{da00e8c3-6096-4698-8f02-18008bcf907d} on package provider:
{083FAB46-0302-4172-8910-07B9A5CF8959}, package: ClientUpdate
[170C:1710][2012-09-10T13:44:14]: ApplyComplete Silent install
[170C:1710][2012-09-10T13:44:14]: Apply complete, result: 0x80070643,
restart: None, ba requested restart: No
[170C:1710][2012-09-10T13:44:14]: Shutting down, exit code: 0x0
[170C:1710][2012-09-10T13:44:14]: Variable: EMBLAIDVAR = 124017
[170C:1710][2012-09-10T13:44:14]: Variable: Netfx35FullVersion =
3.5.30729.01
[170C:1710][2012-09-10T13:44:14]: Variable: Netfx35x64FullVersion =
3.5.30729.01
[170C:1710][2012-09-10T13:44:14]: Variable: Netfx4FullVersion = 4.0.30319
[170C:1710][2012-09-10T13:44:14]: Variable: Netfx4x64FullVersion = 4.0.30319
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleAction = 3
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleElevated = 1
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleInstalled = 1
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleLastUsedSource =
C:\SEGOT-GDP\GTTI\RI_4.001.01\src\GenericTTInstaller\Installer\bin\Debug\
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleLog =
C:\DOCUME~1\v0c8665\LOCALS~1\Temp\Installer_20120910134356.log
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleLog_Fido =
C:\DOCUME~1\v0c8665\LOCALS~1\Temp\Installer_20120910134356_0_Fido.log
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleName = Installer
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleOriginalSource =
C:\SEGOT-GDP\GTTI\RI_4.001.01\src\GenericTTInstaller\Installer\bin\Debug\Installer.exe
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleProviderKey =
{da00e8c3-6096-4698-8f02-18008bcf907d}
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleRollbackLog_Fido =
C:\DOCUME~1\v0c8665\LOCALS~1\Temp\Installer_20120910134356_0_Fido_rollback.log
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleTag =
[170C:1710][2012-09-10T13:44:14]: Variable: WixBundleVersion = 1.0.0.0
[170C:1710][2012-09-10T13:44:15]: Exit code: 0x0, restarting: No


Could use some help here....

Kind regards,
Caisa



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Really-weird-upgrade-problem-tp7580416.html
Sent from the wix-users mailing list archive at Nabble.com.
Tim Comport
13 years ago
Permalink
This sounds very similar (the same) to the problem I have been struggling
with for a while.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Upgrade-Issue-tt7579392.html
Just did some more testing today, about to update above thread with my
findings.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Really-weird-upgrade-problem-tp7580416p7580438.html
Sent from the wix-users mailing list archive at Nabble.com.
Miss Parker
13 years ago
Permalink
Ok, thanks. I'll keep an eye on your thread.

//Caisa



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Really-weird-upgrade-problem-tp7580416p7580441.html
Sent from the wix-users mailing list archive at Nabble.com.
Miss Parker
13 years ago
Permalink
I'm bumping this thread since I really need help with this problem.

In a nutshell, the question is this:

*During an upgrade, what can cause that one of the /unchanged/ msi's won't
get the new bundle id registered as a dependency in the registry, which
makes Burn wanting to uninstall it?*

This is pretty much the gist. Hopefully one of the Burn developers can give
me some insight....

//Caisa



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Really-weird-upgrade-problem-tp7580416p7580466.html
Sent from the wix-users mailing list archive at Nabble.com.
Rob Mensching
13 years ago
Permalink
There are a number of mysterious things in this log that need more
information to debug. For example:

[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
2.1.0.0, language: 0 operation: MajorUpgrade
[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
2.1.0.0, language: 0 operation: Downgrade
What is this related package? Why is it both and upgrade and a downgrade?
Are you sharing an UpgradeCode across MSIs or something?


[170C:1710][2012-09-10T13:43:58]: Detected related
bundle:{c7b317c5-8468-4316-be7f-044b329ffcd8}, type: Upgrade, scope:
PerMachine, version: 1.1.0.0, operation: None
What is this related bundle? Your scenario didn't discuss 1.1.0.0... is
this left over from a previous bundle install?

I agree that the issue sounds to be dependents:

[170C:1710][2012-09-10T13:43:58]: Will not uninstall package: ClientUpdate,
found dependents: 1
[170C:1710][2012-09-10T13:43:58]: Found dependent:
{c7b317c5-8468-4316-be7f-044b329ffcd8}, name: Installer
ClientUpdate seems okay. Why was Fido missing its dependency. Did the Fido
ProductCode change between bundles?

My best guess is dirty machine or strange rebuild but it is kinda'
mysterious. Seeing the different bundles may make it clearer. Simplifying
the repro may help as well.
...
--
virtually,

Rob Mensching
http://RobMensching.com LLC
Miss Parker
13 years ago
Permalink
/[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
2.1.0.0, language: 0 operation: MajorUpgrade
[170C:1710][2012-09-10T13:43:58]: Detected related
package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:
2.1.0.0, language: 0 operation: Downgrade
What is this related package? Why is it both and upgrade and a downgrade?
Are you sharing an UpgradeCode across MSIs or something?
/

This related package is the updated msi - Branding. I don't know why this is
both upgrade and downgrade, the msi is not something I have built. The same
behaviour is present in the test bootstrapper where the upgrade works. I
don't think that upgrade codes are shared.

/
[170C:1710][2012-09-10T13:43:58]: Detected related
bundle:{c7b317c5-8468-4316-be7f-044b329ffcd8}, type: Upgrade, scope:
PerMachine, version: 1.1.0.0, operation: None
What is this related bundle? Your scenario didn't discuss 1.1.0.0... is
this left over from a previous bundle install? /

Yeah, my bad...after reading a million log files I mixed them up. The
original bundle version is 1.0.0.0 and the above version is from the upgrade
bundle.

/[170C:1710][2012-09-10T13:43:58]: Will not uninstall package: ClientUpdate,
found dependents: 1
[170C:1710][2012-09-10T13:43:58]: Found dependent:
{c7b317c5-8468-4316-be7f-044b329ffcd8}, name: Installer
ClientUpdate seems okay. Why was Fido missing its dependency. Did the Fido
ProductCode change between bundles?
/

No, that's the weird thing, I'm using the exact same files during the
upgrade, except of course for the Branding msi.

The real confusing thing is that this works with the test bootstrapper
(based on WixBA), but not with our "real" bootstrapper application. The
differences between the projects are mostly GUI related so we don't think
this relates to the problem, and except for the upgrade code and Name their
bundles are identical.

I've attached the two bundles, but the only difference between them are
versions and an upgraded msi.

Thank you very much for taking time with this.

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7580512/Bundle_original.txt
Bundle_original.txt

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7580512/Bundle_upgrade.txt
Bundle_upgrade.txt


//Caisa




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Really-weird-upgrade-problem-tp7580416p7580512.html
Sent from the wix-users mailing list archive at Nabble.com.

Continue reading on narkive:
Loading...