Miller, Bill (QuickWire)
2013-07-04 17:08:36 UTC
Hi all, I have an issue with ONE user running my shiny new wix bundle.
The error (0x80004005) as we all know is Access Denied, I've tried extensively to reproduce this for a couple days now and I'm at a loss.
Any errors like this I've found refer to signed bundles -- which I don't do (msi or exe).
Here's some info about the system having the issue:
Windows 2003 R2 SP2 (v5.2.3790)
An older bundle was installed, as well as a separate older (main) MSI.
The system has an AV on it (Vipre Business) - I asked the user to disable it for the install but I'm not sure they've actually done it.
User is logged in as local admin.
OS is patched up to date and has Root Certificates installed - if that's required for unsigned bundles, just saying.
Here's a snippet from the burn log, all previous entries show exactly as expected (ie identical to a working install)
[0DB8:0DBC][2013-07-03T09:17:57]i000: Caching bundle from: 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\{8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}\.be\QW_Server_v6.54.1.exe' to: 'C:\Documents and Settings\All Users\Application Data\Package Cache\{8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}\QW_Server_v6.54.1.exe'
[0DB8:0DBC][2013-07-03T09:17:57]i320: Registering bundle dependency provider: {8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}, version: 6.54.1.0
[0D7C:0E10][2013-07-03T09:17:57]i336: Acquiring container: WixAttachedContainer, copy from: C:\Documents and Settings\Administrator\Desktop\Quickwire Items\6-54-1\QW_Server_v6.54.1.exe
[0D7C:0E10][2013-07-03T09:17:57]i000: Setting string variable 'WixBundleLastUsedSource' to value 'C:\Documents and Settings\Administrator\Desktop\Quickwire Items\6-54-1\'
[0D7C:0E14][2013-07-03T09:17:57]e000: Error 0x80004005: Failed to extract all files from container.
So here is a snippet from a log that worked fine running on the same OS:
[0F98:0F6C][2013-07-04T12:10:37]i000: Caching bundle from: 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}\.be\QW_Server_v6.54.1.exe' to: 'C:\Documents and Settings\All Users\Application Data\Package Cache\{8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}\QW_Server_v6.54.1.exe'
[0F98:0F6C][2013-07-04T12:10:37]i320: Registering bundle dependency provider: {8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}, version: 6.54.1.0
[0F98:0ED4][2013-07-04T12:10:44]i305: Verified acquired payload: QW_Server_v6.54.1_x86.msi at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\QW_Server_v6.54.1_x86.msi, moving to: C:\Documents and Settings\All Users\Application Data\Package Cache\{0B46DA8B-EDA7-43B9-B3F1-70633F4401A5}v6.54.1\QW_Server_v6.54.1_x86.msi.
[0F98:0F6C][2013-07-04T12:10:44]i323: Registering package dependency provider: {0B46DA8B-EDA7-43B9-B3F1-70633F4401A5}, version: 6.54.1, package: QW_Server_v6.54.1_x86.msi
[0F98:0F6C][2013-07-04T12:10:45]i301: Applying execute package: QW_Server_v6.54.1_x86.msi, action: Install, path: C:\Documents and Settings\All Users\Application Data\Package Cache\{0B46DA8B-EDA7-43B9-B3F1-70633F4401A5}v6.54.1\QW_Server_v6.54.1_x86.msi, arguments: ' MSIFASTINSTALL="7" SKIPLICENSE="1"'
Everything blows up after the ": Registering bundle dependency provider" message.
The failed install then logs "Acquiring container" and sets the last "WixBundleLastUsedSource' variable.
This is a production machine so I don't have access to it. It seems that Burn is looking for the previous bundle or something?
Try as I might I cannot reproduce this.
I had the user manually uninstall (via ARP) the previous bundle and the MSI (that was installed later separately) but re-install fails the same.
I created a Win 2003 VM and try as I might I cannot reproduce the issue. In fact Burn works perfectly regardless of what I throw at it.
I've tried deleting the temp & Package Cache folders and everything runs fine (had the user do that as well).
I've even removed access to the SYSTEM user to these folders and managed a failed extraction but the log was different (and obvious).
I've also installed their AV and couldn't get it to fail - not that I really expected it to.
All packages in my Bundle are set to NOT uninstall with the Bundle. Maybe this isn't very 'bundlely' of me but my MSI has its own interface and can be installed separately.
That said, when I run a new bundle everything updates perfectly as expected.
I'm getting around this by simply sending the user the MSI - since all perquisites are installed.
I love the 'Bundle' idea, took me awhile but it's the smart way to go...
Any ideas about what to look for or a next step?
Is there a known sequence of operations that can cause this? - I read about renaming MSI's then installing,deleting and uninstalling etc, but Burn handled it ALL with a burp.
Can I waste a registry entry somewhere to get by this?
I'm terrified this will pop up elsewhere and I'm not used to having zero answers for my users.
This is my one and only wix problem for a pretty large install (120+ meg).
Thanks to anyone who made it this far.
Bill
The error (0x80004005) as we all know is Access Denied, I've tried extensively to reproduce this for a couple days now and I'm at a loss.
Any errors like this I've found refer to signed bundles -- which I don't do (msi or exe).
Here's some info about the system having the issue:
Windows 2003 R2 SP2 (v5.2.3790)
An older bundle was installed, as well as a separate older (main) MSI.
The system has an AV on it (Vipre Business) - I asked the user to disable it for the install but I'm not sure they've actually done it.
User is logged in as local admin.
OS is patched up to date and has Root Certificates installed - if that's required for unsigned bundles, just saying.
Here's a snippet from the burn log, all previous entries show exactly as expected (ie identical to a working install)
[0DB8:0DBC][2013-07-03T09:17:57]i000: Caching bundle from: 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\{8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}\.be\QW_Server_v6.54.1.exe' to: 'C:\Documents and Settings\All Users\Application Data\Package Cache\{8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}\QW_Server_v6.54.1.exe'
[0DB8:0DBC][2013-07-03T09:17:57]i320: Registering bundle dependency provider: {8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}, version: 6.54.1.0
[0D7C:0E10][2013-07-03T09:17:57]i336: Acquiring container: WixAttachedContainer, copy from: C:\Documents and Settings\Administrator\Desktop\Quickwire Items\6-54-1\QW_Server_v6.54.1.exe
[0D7C:0E10][2013-07-03T09:17:57]i000: Setting string variable 'WixBundleLastUsedSource' to value 'C:\Documents and Settings\Administrator\Desktop\Quickwire Items\6-54-1\'
[0D7C:0E14][2013-07-03T09:17:57]e000: Error 0x80004005: Failed to extract all files from container.
So here is a snippet from a log that worked fine running on the same OS:
[0F98:0F6C][2013-07-04T12:10:37]i000: Caching bundle from: 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}\.be\QW_Server_v6.54.1.exe' to: 'C:\Documents and Settings\All Users\Application Data\Package Cache\{8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}\QW_Server_v6.54.1.exe'
[0F98:0F6C][2013-07-04T12:10:37]i320: Registering bundle dependency provider: {8dc70ff1-c6e5-43d3-b30f-97f2be8765ab}, version: 6.54.1.0
[0F98:0ED4][2013-07-04T12:10:44]i305: Verified acquired payload: QW_Server_v6.54.1_x86.msi at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\QW_Server_v6.54.1_x86.msi, moving to: C:\Documents and Settings\All Users\Application Data\Package Cache\{0B46DA8B-EDA7-43B9-B3F1-70633F4401A5}v6.54.1\QW_Server_v6.54.1_x86.msi.
[0F98:0F6C][2013-07-04T12:10:44]i323: Registering package dependency provider: {0B46DA8B-EDA7-43B9-B3F1-70633F4401A5}, version: 6.54.1, package: QW_Server_v6.54.1_x86.msi
[0F98:0F6C][2013-07-04T12:10:45]i301: Applying execute package: QW_Server_v6.54.1_x86.msi, action: Install, path: C:\Documents and Settings\All Users\Application Data\Package Cache\{0B46DA8B-EDA7-43B9-B3F1-70633F4401A5}v6.54.1\QW_Server_v6.54.1_x86.msi, arguments: ' MSIFASTINSTALL="7" SKIPLICENSE="1"'
Everything blows up after the ": Registering bundle dependency provider" message.
The failed install then logs "Acquiring container" and sets the last "WixBundleLastUsedSource' variable.
This is a production machine so I don't have access to it. It seems that Burn is looking for the previous bundle or something?
Try as I might I cannot reproduce this.
I had the user manually uninstall (via ARP) the previous bundle and the MSI (that was installed later separately) but re-install fails the same.
I created a Win 2003 VM and try as I might I cannot reproduce the issue. In fact Burn works perfectly regardless of what I throw at it.
I've tried deleting the temp & Package Cache folders and everything runs fine (had the user do that as well).
I've even removed access to the SYSTEM user to these folders and managed a failed extraction but the log was different (and obvious).
I've also installed their AV and couldn't get it to fail - not that I really expected it to.
All packages in my Bundle are set to NOT uninstall with the Bundle. Maybe this isn't very 'bundlely' of me but my MSI has its own interface and can be installed separately.
That said, when I run a new bundle everything updates perfectly as expected.
I'm getting around this by simply sending the user the MSI - since all perquisites are installed.
I love the 'Bundle' idea, took me awhile but it's the smart way to go...
Any ideas about what to look for or a next step?
Is there a known sequence of operations that can cause this? - I read about renaming MSI's then installing,deleting and uninstalling etc, but Burn handled it ALL with a burp.
Can I waste a registry entry somewhere to get by this?
I'm terrified this will pop up elsewhere and I'm not used to having zero answers for my users.
This is my one and only wix problem for a pretty large install (120+ meg).
Thanks to anyone who made it this far.
Bill