[WiX-users] Bundle gets installed side-by-side even with same upgradecode

[victorwhiskey]

Hello,

I'm testing my upgrade scenario and I am using a bundle to install 2 MSI
packages. The MSI packages have a new version number as well as the bundle.
So I have three entries in ARP 2 for the MSIs and one for the bundle,
originally. After I upgrade, the two MSI entries are upgrades but the bundle
is installed side-by-side with the old one. Now I have four entries the two
MSIs and a bundle entry 2.0.0.0 and 2.0.3.0, for example.

The burn log indicates a removal of the old bundle, however it is still
there. I am using WIX v3.6.3303.0.

[0D30:0D34][2013-01-17T18:00:23]: Setting string variable
'NETFRAMEWORK40CLIENT' to value '1'
[0D30:0D34][2013-01-17T18:00:23]: Detected related bundle:
{ef7da9a5-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, type: Upgrade, scope: PerMachine,
version: 2.0.0.4, operation: MajorUpgrade
...
[0D30:0D34][2013-01-17T18:00:26]: Apply begin
...
[0D94:0DA8][2013-01-17T18:00:29]: Verified existing payload: xxxPatch at
path: C:\Documents and Settings\All Users\Application Data\Package
Cache\F3BAC218E6E67D4BD2xxxxxxxxxxxxxxxxxxxxxx\xxxPatch.exe.
[0D94:0DA8][2013-01-17T18:00:29]: Error 0x80070002: Failed to find payload:
QPackage in working path:
C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\{15a6c405-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\QPackage
and unverified path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\QPackage
[0D94:0DA8][2013-01-17T18:00:29]: Error 0x80070002: Failed to cache payload:
QPackage
[0D30:0DBC][2013-01-17T18:00:29]: Failed to cache payload: QPackage from
working path:
C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\{15a6c405-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\QPackage,
error: 0x80070002.
[0D30:0DBC][2013-01-17T18:00:29]: Application requested retry of payload:
QPackage, encountered error: 0x80070002. Retrying...
[0D94:0DA8][2013-01-17T18:00:29]: Verified acquired payload: QPackage at
path: C:\Documents and Settings\All Users\Application Data\Package
Cache\.unverified\QPackage, moving to: C:\Documents and Settings\All
Users\Application Data\Package
Cache\{5FCEB634-xxxx-xxxx-xxxx-xxxxxxxxxxxx}v2.0.17.0\QSetup.msi.
[0D94:0DA8][2013-01-17T18:00:29]: Error 0x80070002: Failed to find payload:
SPackage in working path:
C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\{15a6c405-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\SPackage
and unverified path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\SPackage
[0D94:0DA8][2013-01-17T18:00:29]: Error 0x80070002: Failed to cache payload:
SPackage
[0D30:0DBC][2013-01-17T18:00:29]: Failed to cache payload: SPackage from
working path:
C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\{15a6c405-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\SPackage,
error: 0x80070002.
[0D30:0DBC][2013-01-17T18:00:29]: Application requested retry of payload:
SPackage, encountered error: 0x80070002. Retrying...
[0D94:0DA8][2013-01-17T18:00:30]: Verified acquired payload: SPackage at
path: C:\Documents and Settings\All Users\Application Data\Package
Cache\.unverified\SPackage, moving to: C:\Documents and Settings\All
Users\Application Data\Package
Cache\{B190FF8E-xxxx-xxxx-xxxx-xxxxxxxxxxxx}v2.0.17\S Setup.msi.
...
[0D94:0D98][2013-01-17T18:01:18]: Registering dependency:
{15a6c405-xxxx-xxxx-xxxx-xxxxxxxxxxxx} on package provider:
{B190FF8E-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, package: SPackage
[0D94:0D98][2013-01-17T18:01:18]: Applying execute package:
{ef7da9a5-ada1-4e96-99a3-17c9bcaf7d5c}, action: Uninstall, path:
C:\Documents and Settings\All Users\Application Data\Package
Cache\{ef7da9a5-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\Setup.exe, arguments:
'"C:\Documents and Settings\All Users\Application Data\Package
Cache\{ef7da9a5-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\Setup.exe" -uninstall -quiet
-burn.related.upgrade'
[0D94:0D98][2013-01-17T18:01:21]: Removed package dependency provider:
{ef7da9a5-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, package:
{ef7da9a5-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
[0D30:0D34][2013-01-17T18:01:21]: Applied execute package:
{ef7da9a5-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, result: 0x0, restart: None
...
[0D30:0D34][2013-01-17T18:02:20]: Apply complete, result: 0x0, restart:
Required, ba requested restart: No


I have a hardcoded upgradecode and I even tried to put in the
<RelatedBundle> with action="Upgrade"... element referencing the same
upgradecode as in the two packages, but the same results.


What am I missing? Any help always appreciated.

Thanks



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999.html
Sent from the wix-users mailing list archive at Nabble.com.

[victorwhiskey]

I was also wondering if I really need to be worried about the errors
mentioned.

0D94:0DA8][2013-01-17T18:00:29]: Error 0x80070002: Failed to find payload:
QPackage in working path:
C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\{15a6c405-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\QPackage
and unverified path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\QPackage
[0D94:0DA8][2013-01-17T18:00:29]: Error 0x80070002: Failed to cache payload:
QPackage
[0D30:0DBC][2013-01-17T18:00:29]: Failed to cache payload: QPackage from
working path:
C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\{15a6c405-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\QPackage,
error: 0x80070002.

I have the following in ResolveSource

private void ResolveSource(object sender, ResolveSourceEventArgs e)
{
if (!string.IsNullOrEmpty(e.DownloadSource))
{
e.Result = Result.Download;
}
else
{
e.Result = Result.None;
}
}

Thanks



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7583027.html
Sent from the wix-users mailing list archive at Nabble.com.

[victorwhiskey]

Can any give any hints to why the bundle is installing side-by side and what
I can do?

Thank you for your help.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7583130.html
Sent from the wix-users mailing list archive at Nabble.com.

[Rob Mensching]

The 0x80002 errors sound just like the mysterious issue we were trying to
hunt down that doesn't show up on all machines. It seems files are getting
deleted out of the working folder before we have a chance to move them to
the secure cache. Can't see anything in our code doing that so we're
wondering if it is an external process doing it.

It would be interesting if you hooked up ProcessMonitor and watched the
paths to see what ends up deleting the file that Burn ends up erroring on.

Post by victorwhiskey
Can any give any hints to why the bundle is installing side-by side and what
I can do?
Thank you for your help.
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7583130.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users

[victorwhiskey]

Thanks Rob,

For the 0x80002 issue, are the packages supposed to be left in the
%temp%\{guid}\ directories after install? I see this when testing upgrade
and found out they are removed after the initial installation. I hooked up
ProcessorMonitor and saw after the install, it was removing the contents of
the %temp%\{guid} directory.

deleting_self.PNG
<Loading Image...>

Also, any tips for "After I upgrade, the two MSI entries are upgrades but
the bundle is installed side-by-side with the old one. Now I have four
entries the two MSIs and a bundle entry 2.0.0.0 and 2.0.3.0, for example. "

I'd like my bundle to not install if 2.0.0.0 and new package is 2.0.0.7,
lets say, but will upgrade if 2.0.0 to 2.0.3.0.

Thanks again!



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7583170.html
Sent from the wix-users mailing list archive at Nabble.com.

[Rob Mensching]

Yes, the directories are all cleaned up in the end. The question is what is
cleaning up the file that is mentioned in the log file in the middle of the
install. That's what is causing the failure.

Post by victorwhiskey
Thanks Rob,
For the 0x80002 issue, are the packages supposed to be left in the
%temp%\{guid}\ directories after install? I see this when testing upgrade
and found out they are removed after the initial installation. I hooked up
ProcessorMonitor and saw after the install, it was removing the contents of
the %temp%\{guid} directory.
deleting_self.PNG
<
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7583170/deleting_self.PNG
Also, any tips for "After I upgrade, the two MSI entries are upgrades but
the bundle is installed side-by-side with the old one. Now I have four
entries the two MSIs and a bundle entry 2.0.0.0 and 2.0.3.0, for example. "
I'd like my bundle to not install if 2.0.0.0 and new package is 2.0.0.7,
lets say, but will upgrade if 2.0.0 to 2.0.3.0.
Thanks again!
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7583170.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users

[victorwhiskey]

Hey guys,

I'm still seeing the issue, multiple entries in ARP for the bundle.

The following is the log file of the bundle upgrade.

[0A50:0A54][2013-02-06T07:07:20]: Burn v3.6.3303.0, Windows v5.1 (Build
2600: Service Pack 3), path: C:\Documents and Settings\All Users\Application
Data\Package Cache\{aaaaaaaa-ab16-4053-92ac-bbbbbbbbbbbb}\SW Setup.exe,
cmdline: '-uninstall -quiet -burn.related.upgrade -burn.embedded
BurnPipe.{xxxxxxxx-2790-4AE5-9B23-xxxxxxxxxxxx}
{yyyyyyyy-2A75-4DE5-8B0C-yyyyyyyyyyyy} 3920'
[0A50:0A54][2013-02-06T07:07:20]: This bundle is being run by a related
bundle as type 'Upgrade'.
[0A50:0A54][2013-02-06T07:07:20]: Setting string variable 'WixBundleLog' to
value 'C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\SW_Setup_20130206070720.log'
[0A50:0A54][2013-02-06T07:07:20]: Loading managed bootstrapper application.
[0A50:0A54][2013-02-06T07:07:21]: Creating BA thread to run asynchronously.
[0A50:0A54][2013-02-06T07:07:21]: Shutting down, exit code: 0x0
[0A50:0A44][2013-02-06T07:07:21]: Running the WDUX BA.
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleAction = 3
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleElevated = 0
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleInstalled = 1
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleLog =
C:\DOCUME~1\TESTAD~1\LOCALS~1\Temp\SW_Setup_20130206070720.log
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleName = WD SmartWare
Setup
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleOriginalSource =
C:\Documents and Settings\testAdmin\Desktop\021\SWSetup.exe
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleProviderKey =
{aaaaaaaa-ab16-4053-92ac-bbbbbbbbbbbb}
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleTag =
[0A50:0A54][2013-02-06T07:07:21]: Variable: WixBundleVersion = 2.0.0.21
[0A50:0A54][2013-02-06T07:07:21]: Exit code: 0x0, restarting: No


It seems like it is working partially because if I go into ARP and manually
remove the old bundle, it removes fine, and does not remove the other
packages.

What am I missing?

Thanks



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7583392.html
Sent from the wix-users mailing list archive at Nabble.com.

[Bob Arnson]

Post by victorwhiskey
[0A50:0A54][2013-02-06T07:07:20]: Loading managed bootstrapper application.
[0A50:0A54][2013-02-06T07:07:21]: Creating BA thread to run asynchronously.
[0A50:0A54][2013-02-06T07:07:21]: Shutting down, exit code: 0x0
[0A50:0A44][2013-02-06T07:07:21]: Running the WDUX BA.

Your BA isn't handling something correctly, since it appears to just
shut down immediately.

[victorwhiskey]

Bob,

Unfortunately, I'm don't even know where to start looking. Actually, I'm
currently not handling anything because from what I've read, the bundle
should self upgrade and remove older entries from ARP if it detects a newer
version, but then I've also read these threads,
http://stackoverflow.com/questions/11572508/how-to-do-major-upgrades-when-using-burn-wix-3-6
and
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Upgrade-Detection-td7580471.html

Where is the place I should start looking? DetectedRelatedBundle,
DetectBegin? Also, after upgrading, and I go into ARP, I can go and
uninstall the older version through there no problem. Is that different than
uninstalling on upgrade?

Thanks



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7583470.html
Sent from the wix-users mailing list archive at Nabble.com.

[Kristian Jaksch]

I think I'm seeing the same issue as you are. I made a minimal managed
bootstrapper and tried to follow all available tutorials on how to do this
but the new version is always installed side by side with the previous
version. If I switch from my custom managed bootstrapper to a default one
the previous version is replaced by the new one as supposed. I posted my
project on the list here and I'll see if someone might look at it and see
what's wrong with my solution. I haven't been able to find a fully working
sample to download except from the WixBA custom bootstrapper but that's a
bit too heavy for me to start with.

Cheers

/Kristian

Post by victorwhiskey
Bob,
Unfortunately, I'm don't even know where to start looking. Actually, I'm
currently not handling anything because from what I've read, the bundle
should self upgrade and remove older entries from ARP if it detects a newer
version, but then I've also read these threads,
http://stackoverflow.com/questions/11572508/how-to-do-major-upgrades-when-using-burn-wix-3-6
and
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Upgrade-Detection-td7580471.html
Where is the place I should start looking? DetectedRelatedBundle,
DetectBegin? Also, after upgrading, and I go into ARP, I can go and
uninstall the older version through there no problem. Is that different than
uninstalling on upgrade?
Thanks
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7583470.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users

[Santhos]

Has anybody solved the upgrade problem?

Try to use one RelatedBundle element only with Action="Upgrade".

The advice I quote has not helped me.

My installer is a very simple hyperlink installer
(WixStandardBootstrapperApplication.HyperlinkLicense) with custom UI:
bundle.wxs, theme.wxl and theme.xml, where the theme is a almost a copy of
the hyperlink default theme.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-gets-installed-side-by-side-even-with-same-upgradecode-tp7582999p7589126.html
Sent from the wix-users mailing list archive at Nabble.com.