Open rkieslinger opened 6 years ago
There might be an issue with globals with the sync/async mix.
We have such kind of error even without sync/async mix. It happens occasionally and very rare. The interesting thing about it is that WiX is able to call a few CAs with the same declaration (Return="check" Execute="firstSequence") and then fails with error: SFXCA: Failed to create communication pipe for new CA process. Error code: 231
Here is the piece of the log:
MSI (c) (4C:1C) [16:23:51:215]: Doing action: CheckAppInstalled Action 16:23:51: CheckAppInstalled. Action start 16:23:51: CheckAppInstalled. MSI (c) (4C:A0) [16:23:51:480]: Invoking remote custom action. DLL: C:\Users_\AppData\Local\Temp\MSI5BAA.tmp, Entrypoint: CheckAppInstalled SFXCA: Extracting custom action to temporary directory: C:\Users_\AppData\Local\Temp\MSI5BAA.tmp-\ SFXCA: Binding to CLR version v4.0.30319 Calling custom action PluginInstaller.CustomActions!PluginInstaller.CustomActions.InstallerCustomActions.CheckAppInstalled Action ended 16:23:52: CheckAppInstalled. Return value 1. MSI (c) (4C:1C) [16:23:52:541]: Doing action: CheckAppVersion Action 16:23:52: CheckAppVersion. Action start 16:23:52: CheckAppVersion. MSI (c) (4C:10) [16:23:52:760]: Invoking remote custom action. DLL: C:\Users_\AppData\Local\Temp\MSI60BA.tmp, Entrypoint: CheckAppVersion SFXCA: Failed to create communication pipe for new CA process. Error code: 231 CustomAction CheckAppVersion returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 16:23:52: CheckAppVersion. Return value 3.
Failed to create communication pipe for new CA process. Error code: 231
Log
Code for reproduction