WiLogUtl.exe does not work with Windows Installer 3.1 log files

A little while back I described a method of searching for errors in a verbose MSI log file.  At the end of that post, I listed an MSI log parsing tool named wilogutl.exe that ships as a part of the Windows Installer Platform SDK.  I found out today that this tool does not parse log files created by Windows Installer 3.1.  If you try to parse an MSI 3.1 log file with wilogutl.exe, you will see an error dialog that says “Log file created with version higher than this tool supports”.

This is a known issue with wilogutl.exe that still needs to be addressed.  In the meantime, you can do the following to workaround this:

  1. Open the verbose log file in a text editor such as notepad
  2. Change the version number in the first line of the log file from 3.01.xxxx.xxxx to 3.00.xxxx.xxxx
  3. Save and close the verbose log file
  4. Run wilogutl.exe again and load the log file

For example, the following appears in the verbose log file created on my development machine (which is running Windows Server 2003 with SP1) when I installed Visual Studio .NET 2003:

=== Verbose logging started: 8/4/2005  10:40:02  Build type: SHIP UNICODE 3.01.4000.2435  Calling process: C:\Documents and Settings\astebner\Local Settings\Temp\SIT12447.tmp\setup.exe ===

When I changed it to the following, wilogutl.exe started working correctly for me:

=== Verbose logging started: 8/4/2005  10:40:02  Build type: SHIP UNICODE 3.00.4000.2435  Calling process: C:\Documents and Settings\astebner\Local Settings\Temp\SIT12447.tmp\setup.exe ===

<update 8/23/2005> The newest version of the Windows Installer PSDK contains an updated version of wilogutl.exe that will correctly parse log files produced by Windows Installer 3.1.  The above steps can be used to enable older versions of wilogutl.exe to parse 3.1 log files.


Comments (5)

  1. Martin says:

    I have WiLogUtl.exe v3.1.4000.1830 here and it works ok with 3.01.4000.2435 logfiles. I’m not sure in which Platform SDK version it is included, probably the W2K3SP1 one.


  2. Josh says:

    I believe Martin is correct, the latest Platform SDK includes an updated version of the verbose log analyzer that appears to work with logs created by MSI 3.1.

  3. Hey Martin and Josh – thank you for the follow up posts. It looks like I was using an older version of wilogutl.exe when I reproduced this issue and it is fixed in the most recent Windows Installer PSDK.

    This workaround will still work if you want to avoid downloading the PSDK to get the updated version.

  4. Recently I blogged about beta2 availability of OM2007. I finally got some time to get it installed and…