I encountered the same error recently and I'm wondering what caused it despite the installation wizard flowing through successfully. I already sent the logs and .aip file to the mentioned email address to get some clarity on the issue.
Indeed this worked on an alternative text file when I tried it yesterday.
Anyway, does that mean that the built-in way of logging these custom actions' output is not yet included in 20.2.1 or later? If so, do you have an ETA for it?
Is this already possible in 20.2.1 version? I need to get the output from a .cmd on a 'Launch File' custom action. Output redirection like the one below doesn't seem to work.
File to launch: swcef.cmd
Command line: >>[MsiLogFileLocation] 2>&1
Working directory: [APPDIR]
I have a wizard page that contains two checkboxes with two hyperlinks, but they are not 'linked' in such a way that clicking on the part that says "I have read and accept the" should toggle the checkbox state (checked or unchecked).
Thanks for this! In my case, there was a broken service that had the same name from a previous broken install. It was a head-scratcher until I stumbled upon this post.
An alternative is to copy the custom action name as another key-value pair in action data, but I'm running into a strange issue where, for this particular custom action, the action data becomes blank.
I have a custom action called "DeviceInstall" that calls the "RunCommand" function from an attached DLL, whose execution time is 'deferred'. I also have some other custom actions that call "RunCommand". I already log the function name "RunCommand" in there using Session.Log(...), but I don't know w ...
Noticed this issue recently w/c can be repro'd even w/ single EXE, LZMA compressed, installer made from the latest AI version 20.1.1 Observations:
issue may not happen on the 1st repair, but usually happens on succeeding repairs /extractlzma process shows, in Process Monitor, a repeating SHARING ...