The bad thing is, that the Windows Installer is localized so "Return value 3" is localized too. Be aware of logfiles from your international customer.

The string "value 3" is fine but what if the customer is using German (or other localization) OS?

Example:
MSI (s) (B8:10) [23:47:18:090]: Note: 1: 2262 2: IsolatedComponent 3: -2147287038
Aktion gestartet um 23:47:18: IsolateComponents.
MSI (s) (B8:10) [23:47:18:090]: Doing action: CostFinalize
Aktion beendet um 23:47:18: IsolateComponents. Rückgabewert 1.

"Return value 3" would be "Rückgabewert 3" in a German log. Generally speaking, all actions announce their start and finish in the log. You would see something like this:
Action start 08:40:52: IsolateComponents.
Action ended 08:40:52: IsolateComponents. Return value 0.
The latter row contains something that would translate to "Return value".

Just been putting this tip into practice - very useful!

Thanks - just put this to good use, also sent it on to our helpdesk staff!

First thing I do is open it with WiLogUtl.exe that comes with the windows SDK... I'm not masochistic enough to open a log file in notepad :P

Any idea what it's value 3 instead of some other random number (like 1 or 2)?

Eric,

Custom action return values (http://msdn.microsoft.com/library/aa368072.aspx) get translated into "script" CA return values (http://msdn.microsoft.com/library/aa371254.aspx) and logged that way. Thus, 3 = IDABORT. 1 = IDOK (aka Success!)

Hi all,

the first thing I do with an MSI log is to open with the Microsoft tool "Windows Installer Verbose Log Analyzer" (WiLogUtl.exe).

One Problem is that WiLogUtl.exe support only MSI logs up to MSI version 3.0.0.0.

So if I have a log file from a newer version I first change the version in the first line of the log file using notepad or any better editor.

As example the first line is
=== Verbose logging started: 1/20/2012 8:58:55 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: C:\WINDOWS\system32\msiexec.exe ===

so I change 3.01.4001.5512 to 3.0.0.0 and save the log file. Now WiLogUtl.exe will be able to handle the log file.
Just open the log file an press the "Analyze" button.

Now you get a "Detailed Log File View" dialog from where you could check states, properties etc.

My prefered option is the "HTML Log". Allow Blocked Content is required.
Now you could use the buttons "First Error", "Last Error", "Previous Error" and "Next Error" to navigate.
For better reading the lines are formated in different colors.

When jumping to an error you have to scroll some lines up to find the reason of the error like Rob said in his blog.

Hi guys,

I encourage you to try Legit Log Viewer in favor of legendary Notepad :).

It supports MSI (Windows installer) logs and WiX burn logs out-of-box. And many other formats via XML config files.

Current version doesn't support log headers, so you should remove "=== Verbose logging started:..." string form the beginning of MSI log.

Later we will publish update and add support for log headers. Since I’m personally using it to troubleshoot our installs, it will be sooner than later.