Hello,
It seems that the installation fails because of the TestCA.exe custom action.
Code: Select all
MSI (s) (84:78) [04:50:19:642]: Note: 1: 1722 2: TestCA.exe 3: c:\Program Files (x86)\Your Company\TestApp\Test instalatora\TestCA.exe 4:
CustomAction TestCA.exe returned actual error code -2147450749 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (84:78) [04:50:19:642]: Product: TestApp -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action TestCA.exe, location: c:\Program Files (x86)\Your Company\TestApp\Test instalatora\TestCA.exe, command:
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action TestCA.exe, location: c:\Program Files (x86)\Your Company\TestApp\Test instalatora\TestCA.exe, command:
MSI (s) (84:78) [04:50:19:642]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (84:78) [04:50:19:642]: User policy value 'DisableRollback' is 0
MSI (s) (84:78) [04:50:19:642]: Machine policy value 'DisableRollback' is 0
Action ended 4:50:19: InstallExecute. Return value 3.
If your custom action requires the prerequisite to be installed before being executed, I'm afraid this is a Windows Installer limitation when using an .MSI package.
A prerequisite scheduled during main package (feature-based), when the main package is installed silently, is installed as a post-install prerequisite.
The reason for this is the old Windows limitation that prevents two installation packages from running on a machine at the same time.
With UI these packages are installed right after the user presses the "Install" button and right before the installation of the main package starts.
However, since the main package runs silently (/passive), there is no UI displayed and the dialogs are skipped, the prerequisite will be installed after the main package automatically, to avoid the above mentioned limitation.
You can try adding your custom action after the Finish Execution stage and see if that helps.
Best regards,
Liviu
FOLLOW US
Get the latest news in Application Packaging