[wix-users] Get Debug Information out of Burn-driven MSI installation?

[Reuss, Matthias]

So it seems our systems somehow differ.

My standard system setting (I have Windows 7, MSI 5.0) is that I have no group policy concerning logging activated.
I then activated the "Logging" group policy to voicewarmupx - no effect.
Then activated DisableLoggingFromPackage - no effect either.

To me it looks like Burn sets a logging value when starting the package installation (e.g. using MsiEnableLog), and this overrides whatever is in the MsiLogging property or group policies. BTW, this behaviour would be in accordance with MSI documentation.

Best regards

Matthias

-----Ursprüngliche Nachricht-----
Von: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] Im Auftrag von Phill Hogland
Gesendet: Mittwoch, 18. November 2015 16:48
An: WiX Toolset Users Mailing List
Betreff: Re: [wix-users] Get Debug Information out of Burn-driven MSI installation?

I have a third-party MSI in my bundle chain which internally sets MsiLogging to voicewarmupx and it produces logs with the additional logging (much to my annoyance), in contrast to the other MSI packages in the chain, on a system using MSI 5.0.

Some time ago I set the MSI registry key for voicewarmupx and my recollection is that my remaining MSI packages in the chain also then produced the extra logging.  I have also done this some time ago by setting the Group Policy object.  I don't know if something has changed, but I can't focus on debugging this issue at this time.   

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Reuss, Matthias
Sent: Wednesday, November 18, 2015 9:24 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Get Debug Information out of Burn-driven MSI installation?

Hi Phill,

I have just tried this. Set the MsiLogging property in one MSI package to voicewarmupx and ran int from Burn - got "only" a verbose log.
Ran this same pack from the command line - got debug log.
According to MSI documentation (keyword "Normal logging"), The logging mode specified in MsiEnableLog (which I assume Burn uses) overrides the default logging mode set by the MsiLogging property.

Are you setting voicewarmupx on a different place?

Best regards

Matthias Reuss

-----Ursprüngliche Nachricht-----
Von: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] Im Auftrag von Phill Hogland
Gesendet: Mittwoch, 18. November 2015 16:07
An: WiX Toolset Users Mailing List
Betreff: Re: [wix-users] Get Debug Information out of Burn-driven MSI installation?

No. use voicewarmupx if you like.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Reuss, Matthias
Sent: Wednesday, November 18, 2015 8:59 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: [wix-users] Get Debug Information out of Burn-driven MSI installation?

Hello,

MSI allows to get some debug information exceeding "normal" verbose logging e.g. by setting the MsiLogging property to "voicewarmupx".

I have learnt that Burn handles MSI logging in such a way that chained MSI packages always produce "verbose" log files (voicewarmup), see e.g. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-of-MsiLogging-in-Burn-driven-MSI-td7597242.html

Does this mean that I have no chance to get debug output for a Burn-driven installation?

Best regards

Matthias Reuss

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/