Debugging WIX MSI installer issues

On one particular PC after software installation, whenever user tried to launch the application, software installation configuration dialog was popping up continuously. And this was observed on very few PC’s.

After intense googling I found one thread that discussed about self-repair mechanism of WIX installer and it proved useful.

WIX installer generally logs “Windows Events” which can be referred to find out root cause of issues.

Another way is to inspect log generated by MSI. See below example

msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log"

This screenshot should help for Windows event log based debugging –

 

MSI log in Windows Event Viewer

Here are some quick references for WIX/MSI installer:

Advanced Installer User Guide: Generate MSI logs as per need

Real-World Example: WiX/MSI Application Installer

Windows Installer Guide (on MSDN)

Property Reference (on MSDN)

Good thread on: How to add a WiX custom action that happens only on specific activity (such as “Uninstall”)

Use Debug Diag tool to debug and analyze problems

Microsoft’s “Debug Diag” tool is very helpful diagnostic tool that every developer should be aware of who works on Microsoft technologies -

Below are the benefits of “Debug Diag” tool

1. App crash investigations
2. Memory leak finding for .NET & COM components (i.e.e managed & unmanaged)
3. Performance analysis of application

Provides two tools –

1. Debug Collections – which capture data (dump file & text logs)
2. Debug Analyzers – provides summary of analysis in the form of an HTML page. (Produces an MHT file that opens up in IE)

Additional information on “Debug Diag” tool from Microsoft that can be used for memory leak findings –

1. Download link for ‘Debug Diag’ tool from Microsoft’s website.
• Need to download “DebugDiagx64.msi” for 64 bit OS
2. Link for blog on - How to create rules to capture “Memory Leak”
• This article is written for old version, but concept is the same
3. Link for blog on – Debugging Native memory leaks with Debug Diag
4. Link for blog that describes – Additional options & analysis reports