Windows Installer Deferred execution - how can we log the custom actions running in deferred mode?

Question

In my MSI , I have added 2 custom actions to execute in deferred. I cant see these 2 custom actions in the verbose log to see whether these have executed or not. I can see for all other standard and custom actions executed in immediate mode, but not for deferred. Is this expected behavior ? Please help

Make sure you use the most verbose form of logging, which is: MSIEXEC /i xxxx.msi /L*V C:\temp\yourlog.log etc etc.... — Captain_Planet
I have used same , but I couldn't find deferred custom actions executed or not. — Sandy
Please let us know what tool you use to build the MSI, and what language you use for your custom action? Is it VBScript? If it is VBScript please see the link to the PDF below in my answer and read the section on VBScript (direct link to article). If it still doesn't work, maybe you can put sources on github.com for a quick look? I think I have an answer that shows basic WiX markup for a VBScript custom action, I will dig it up shortly. — Stein Åsmul
I messed up the first answer, too many links and details. Please see new answer with link to a sample project on github.com — Stein Åsmul

Stein Åsmul Stein Åsmul · Accepted Answer · 2019-08-20T12:04:00

WiX & VBScript: Here are some answers showing how you can use VBScript custom actions in MSI properly - combine that with the logging approach shown below and you should find all information in your log that you write there:

Light-Weight Condition Testing using VBScript (WiX markup towards bottom)

C++ Custom Actions and Failures

UPDATE: Most likely your setup has aborted before the custom action was invoked? Or your custom action crashed and returned no error? Normally you will see entries in the log along the lines of:

"Invoking remote custom action"
"Created Custom Action Server with PID DECVAL (0xHEXVAL)."
"Hello, I'm your 32bit Impersonated custom action server."

Etc... Very cosy that last variant. "Howdy doody 32bit server".

Comprehensive Logging: Please enable verbose logging with extra debugging information and use buffer-less log writing. The latter is to avoid lost buffer when custom actions crash. The log file is written directly instead of in batches and this slows down installation dramatically. I would recommended this logging variant for your case:
msiexec.exe /i C:\Path\Your.msi /L*vx! C:\Your.log
Tip: Search for "value 3" in the log file to find errors as explained by Rob Mensching (Wix & Orca author).

MSI Logging: Some more information about msiexec.exe logging in general:

Enable installation logs for MSI installer without any command line arguments.
Stefan Kruger's installsite.org has this section on logging (very good).

WiX MSI Logging: When you use WiX's Visual Studio integration, you can create a new Custom Action project and you can use the built in logging they provide from within the custom action:

[CustomAction]
public static ActionResult CustomAction1(Session session)
{
   session.Log("Begin CustomAction1");

   return ActionResult.Success;
}

C++: The above is for a managed code C# custom action, there is a template (at least there used to be) for C++ as well. I much prefer the latter for minimal dependencies.

Custom Action Logging: Your custom action can write to the log file as follows: MSI Tip: Writing to the Log File from a Custom Action. This is done via custom action code - you might do this already?

Links:

Windows Installer Deferred execution - how can we log the custom actions running in deferred mode?

2 Answers