Re: [WiX-users] Why Does Bundle Prompt For Source During Uninstall?

[Rob M. <ro...@fi...>]

The attached container is stripped (to save [often signification] disk space). Look higher in the log to see what package is requesting to be cached during uninstall. Probably an ExePackage.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: Edwin Castro [mailto:eg...@gm...] 
Sent: Monday, July 13, 2015 4:37 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Why Does Bundle Prompt For Source During Uninstall?

I have a bundle that I have successfully installed. When I try to uninstall I get the following:

[0E54:03D0][2015-07-13T15:34:03]i300: Apply begin
[07F0:0814][2015-07-13T15:34:03]i360: Creating a system restore point.
[07F0:0814][2015-07-13T15:34:10]i361: Created a system restore point.
[0E54:01C4][2015-07-13T15:34:10]w341: Prompt for source of container:
WixAttachedContainer, path: C:\Original\path\to\bundle\setup.exe
[0E54:01C4][2015-07-13T15:34:10]e054: Failed to resolve source for
file: C:\Original\path\to\bundle\setup.exe, error: 0x80070643.
[0E54:01C4][2015-07-13T15:34:10]e000: Error 0x80070643: Failed while prompting for source (original path 'C:\Original\path\to\bundle\setup.exe').
[0E54:01C4][2015-07-13T15:34:10]e311: Failed to acquire container:
WixAttachedContainer to working path:
C:\Windows\TEMP\{e2007576-a648-4b3f-8e4d-eccd898e4591}\75A375A2F5B5EE0C8914C4790878E0D2772E4838,
error: 0x80070643.
[0E54:03D0][2015-07-13T15:34:10]e000: Error 0x80070643: Failed while caching, aborting execution.
[0E54:03D0][2015-07-13T15:34:10]i399: Apply complete, result: 0x80070643,
restart: None, ba requested restart:  No
[0E54:03D0][2015-07-13T15:34:11]i500: Shutting down, exit code: 0x643

I checked C:\ProgramData\Package Cache to make sure my bundle was still cached (it was).

Under what circumstances does the burn engine try to resolve the original bundle location?

I was under the impression that the bundle was cached at C:\ProgramData\Package Cache to avoid needing the original source to be available.

--
Edwin G. Castro