[wix-users] Burn Protocol for ExePackage Usage

[Edwin Castro]

The vcredist bundle gets "stuck" after the log received the "Apply
complete" message:

[0C44:04D8][2015-10-01T15:13:47]: Apply complete, result: 0x0,
restart: None, ba requested restart:  No

I would have expected the "Shutting down" message next followed by the
list of burn variables but these messages are never written to the log
and vcredist is still running but apparently doing nothing.

-- 
Edwin G. Castro

On Thu, Oct 1, 2015 at 3:19 PM, Edwin Castro <egcastr at gmail.com> wrote:
> I have found that vcredist completes installing when installed by my
> bundle when I run my bundle from an elevated command prompt (using my
> credentials) on Windows Server 2008. But vcredist gets "stuck" when my
> bundle is run by the SYSTEM user (think configuration management
> tool).
>
> I'm not sure yet why vcredist doesn't like getting installed by the
> SYSTEM user on Windows Server 2008.
>
> --
> Edwin G. Castro
>
> On Thu, Oct 1, 2015 at 11:14 AM, Edwin Castro <egcastr at gmail.com> wrote:
>> Interesting. I see the problem on Windows Server 2008. So this might
>> be a problem with the interaction of vcredist and Windows Vista /
>> Server 2008?
>>
>> --
>> Edwin G. Castro
>>
>> On Thu, Oct 1, 2015 at 10:51 AM, Michael Suodenjoki
>> <Michael.Suodenjoki at intrasoft-intl.dk> wrote:
>>> Funny, I've seen exactly the same "stuck-behavior" using the vc_redist_x86.exe. The progress-bar just stopped in the midst. Until now I believed it was due to a Windows Update problem as I was testing this on Windows Vista (yes, that old one - but just testing). But perhaps it is a problem with the vc_redist_XX.exe itself?
>>>
>>> The below illustrate what I presently use - I'm not using the ExePackage/@Protocol attribute.
>>>
>>> <?xml version="1.0"?>
>>> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util="http://schemas.microsoft.com/wix/UtilExtension" xmlns:bal="http://schemas.microsoft.com/wix/BalExtension">
>>>
>>>   <?include "..\defines.wxi" ?>
>>>
>>>   <Bundle Name="$(var.ProjectName) $(var.SystemName) $(var.SystemVersion).$(var.SystemRevision)"
>>>           Version="$(var.SystemVersion)0.$(var.SystemRevision)" Manufacturer="$(var.CompanyName)"
>>>           UpgradeCode="{8F199022-8BC5-4947-9B9F-C95684B42239}">
>>>
>>>     <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" >
>>>       <bal:WixStandardBootstrapperApplication
>>>         LicenseFile="$(env.DEV_DIR)\User Documentation\$(env.L)\eula.rtf"
>>>         LogoFile="icon.png"
>>>         ShowVersion="no"
>>>         SuppressOptionsUI="yes" />
>>>     </BootstrapperApplicationRef>
>>>
>>>     <util:RegistrySearch Root="HKLM" Key="SOFTWARE\Microsoft\DevDiv\VC\Servicing\14.0\RuntimeMinimum" Value="Install" Variable="vcredistinstalled" />
>>>
>>>     <Chain>
>>>       <ExePackage Id="vc_redist.x86.exe"
>>>         Name="vc_redist.x86.exe" PerMachine="yes" Permanent="yes" Vital="yes" Compressed="no"
>>>         SourceFile="vc_redist.x86.exe"
>>>         DownloadUrl="http://download.microsoft.com/download/9/3/F/93FCF1E7-E6A4-478B-96E7-D4B285925B00/vc_redist.x86.exe"
>>>         InstallCommand="/q /norestart /ACTION=Install"
>>>         RepairCommand="/q ACTION=Repair /hideconsole"
>>>         UninstallCommand="/q ACTION=Uninstall /hideconsole"
>>>         DetectCondition="vcredistinstalled AND (vcredistinstalled >= 1)" />
>>>
>>>       <RollbackBoundary />
>>>
>>>       <MsiPackage Id="MainPackage" DisplayInternalUI="yes" Vital="yes" Compressed="no" SourceFile="$(var.SourceMsi)"/>
>>>     </Chain>
>>>   </Bundle>
>>> </Wix>
>>>
>>> /Michael
>>>
>>> -----Original Message-----
>>> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Edwin Castro
>>> Sent: 1. oktober 2015 19:36
>>> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
>>> Subject: [wix-users] Burn Protocol for ExePackage Usage
>>>
>>> When is it appropriate to use ExePackage/@Protocol="burn"?
>>>
>>> My bundle contains the vcredist_x86.exe and vcredist_x64.exe bundles.
>>> I thought the WiX documentation was telling me I should set ExePackage/@Protocol="burn" to get "extended progress and error reporting".
>>>
>>> Instead the vcredist bundles seem to get "stuck". By stuck I mean that they install their MSIs and then do nothing... The processes are still running but nothing else is getting written to their log files.
>>>
>>> I assume I'm misunderstanding how ExePackage/@Protocol works. Can somebody help me understand when to set ExePackage/@Protocol and what behavior I should expect?
>>>
>>> --
>>> 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/