[wix-users] Burn Bootstrapper Registration and Cache Missing

[Edwin Castro]

I understand. Unfortunately, it is difficult to use ProcMon in the
past. This behavior I'm looking into doesn't happen with any kind of
consistency. I have only one confirmed instance and one case where
this might have happened based on a customer's description of not
seeing the product listed in Programs and Features but I do not have
logs to confirm. Asking customers to run ProcMon on every install
attempt just in case this occurs in the future.

In the absence of ProcMon data I need to try to understand the source
code and try to formulate possible theories of what happened based on
the data I do have which is log data. Any help in understanding the
source code would be greatly appreciated.

--
Edwin G. Castro


On Thu, Feb 23, 2017 at 7:22 AM, Bob Arnson <bob at firegiant.com> wrote:
> ProcMon is your friend. Use it to monitor the registry and directory paths and see what happened when by whom.
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Edwin Castro
> Sent: Wednesday, 22 February, 2017 21:30
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Subject: [wix-users] Burn Bootstrapper Registration and Cache Missing
>
> I have a weird issue with our burn bootstrapper from WiX 3.9. I'm seeing the following messages (sanitized of product info) in the log:
>
> [0AEC:0530][2017-02-22T17:16:53]i323: Registering package dependency
> provider: {11F485A3-AFBD-411C-BA20-713C3988088F}, version: 1.2.3.0,
> package: package4
> [0AEC:0530][2017-02-22T17:16:53]i301: Applying execute package:
> package4, action: Install, path: C:\ProgramData\Package Cache\{11F485A3-AFBD-411C-BA20-713C3988088F}v1.2.3.0\x64\package4.msi,
> arguments: ' ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"
> [0BEC:0294][2017-02-22T17:17:33]i319: Applied execute package:
> package4, result: 0x0, restart: None
> [0AEC:0530][2017-02-22T17:17:33]i325: Registering dependency:
> {bfd6285c-bead-4a5d-9d52-8dc6fffd0a2a} on package provider:
> {11F485A3-AFBD-411C-BA20-713C3988088F}, package: package4
> [0AEC:0530][2017-02-22T17:17:33]i351: Removing cached package:
> package0, from path: C:\ProgramData\Package Cache\AAB5E2EE8B5AEAFA9FCA609D9226A43B86F580C7\
> [0AEC:0530][2017-02-22T17:17:33]i351: Removing cached package:
> package1, from path: C:\ProgramData\Package Cache\96B377A27AC5445328CBAAE210FC4F0AAA750D3F\
> [0AEC:0530][2017-02-22T17:17:33]i351: Removing cached package:
> package2, from path: C:\ProgramData\Package Cache\1A5D93DDDBC431AB27B1DA711CD3370891542797\
> [0AEC:0530][2017-02-22T17:17:33]i351: Removing cached package:
> package3, from path: C:\ProgramData\Package Cache\1AED5244E6E4D28B322134EA0AA222AF18A265BF\
> [0AEC:0530][2017-02-22T17:17:33]e000: Error 0x80070002: Failed to open registration key.
> [0AEC:0530][2017-02-22T17:17:33]e000: Error 0x80070002: Failed to suspend registration session.
> [0BEC:0294][2017-02-22T17:17:33]e000: Error 0x80070002: Failed to end session in per-machine process.
> [0BEC:0294][2017-02-22T17:17:33]i399: Apply complete, result: 0x0,
> restart: None, ba requested restart:  No
> [0BEC:0294][2017-02-22T17:17:33]i500: Shutting down, exit code: 0x0
>
> Burn completes successfully *BUT* there is no registration for the bootstrapper in the registry (under Wow6432Node) so we don't see anything in Programs and Features! I was able to confirm that the registration for the 64-bit package4.msi exists in the registry with SystemComponent=1. The 32-bit registration for the bootstrapper is completely missing.
>
> I also see that the bootstrapper setup.exe does not appear anywhere in C:\ProgramData\Package Cache.
>
> I do see the following in the log:
>
> [0BEC:0294][2017-02-22T17:15:44]i300: Apply begin
> [0AEC:0530][2017-02-22T17:15:44]i360: Creating a system restore point.
> [0AEC:0530][2017-02-22T17:15:44]i362: System restore disabled, system restore point not created.
> [0AEC:0530][2017-02-22T17:15:44]i000: Caching bundle from:
> 'C:\Windows\TEMP\{bfd6285c-bead-4a5d-9d52-8dc6fffd0a2a}\.be\setup.exe'
> to: 'C:\ProgramData\Package
> Cache\{bfd6285c-bead-4a5d-9d52-8dc6fffd0a2a}\setup.exe'
> [0AEC:0530][2017-02-22T17:15:44]i320: Registering bundle dependency
> provider: {bfd6285c-bead-4a5d-9d52-8dc6fffd0a2a}, version: 1.2.0.3
>
> confirming that setup.exe was written to C:\ProgramData\Package Cache when Apply begin started.
>
> I don't see any log messages to confirm that the bootstrapper registration was ever written but I imagine it was written as well.
>
> This all looks like something deleted the package cache for my setup.exe and deleted the registration for setup.exe but everything else stayed in place. I can't figure out what might have caused this.
>
> I was trying to construct a stack trace given the Error messages above but I'm not succeeding. Any help in understanding which RegOpen call failed leading to a "suspend registration session" failure leading to an "end session in per-machine process" failure would be greatly appreciated.
>
> I'm also trying to understand when the setup.exe registration actually gets written to the registry and when setup.exe is cached to C:\ProgramData\Package Cache. Any help there would also be greatly appreciated.
>
> --
> Edwin G. Castro
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/