Hi Colin,
The
AI_ResolveLocalizedCredentials action is added automatically in a project if we detect some scenario regarding
user or group accounts localization.
As it looks like, the installation seems to fail during the upgrade phase, while the old version is uninstalled.
The previous action that was executed before the error is the
RemoveExistingProducts
Action start 9:21:50: RemoveExistingProducts.
MSI (s) (7C:08) [09:21:50:555]: Resetting cached policy values
MSI (s) (7C:08) [09:21:50:555]: Machine policy value 'Debug' is 0
MSI (s) (7C:08) [09:21:50:555]: ******* RunEngine:
So, the error from the log could be related with the previous version that failed to be removed, as later in the log the custom action that failed is the
RemoveExistingProducts.
CustomAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 9:21:52: RemoveExistingProducts. Return value 3.
Action ended 9:21:52: INSTALL. Return value 3.
When a package is installed, Windows caches the MSI by placing it in the
Windows\installer folder. During this process, all the unnecessary information is removed in order to decrease the size of the file. As it looks like, the related dll that handles the localization was also removed, thus when the custom action was scheduled for execution, it failed.
In this case, can you please advise your user to try to manually remove the previous version from the Control Panel to see if this is the case? If the previous version can be removed manually from the Control Panel, then the user can try to install the new version. If the user is unable to remove the installed version, you can advise to run the setup of the previous version and when entering the
maintenance sequence, to select the
Uninstall option.
If you run the same installation package for the second time then Windows Installer will run the installer in maintenance mode and the user will then be presented with choices to alter the installed product, repair it or remove it (done through the MaintenanceTypeDlg). You may need to give access to your user to the setup package they had installed, he might not have the original setup.
Let me know if that helped.
Best regards,
Dan