Hello Michael, Thank you for your preliminary analysis and the valuable suggestion to modify the remove condition by adding "... AND Not UPGRADINGPRODUCTCODE". This modification indeed allows for upgrading the main installer when the chained installer was not modified. I also checked the scenario with upgrading both installers with this condition and your method allowed for performing the "double major upgrade" as well without making any additional modifications in the main installer. Yet, I would like to pose some questions in this respect: 1.Does the failure of the main setup in the major upgrade scenario described in my previous post occur due to a bug in the ISChainPackage... CAs implementation or one can find some references about its cause in the MSI documentation? Why does the install log file not contain the explicit error reference? 2. Do you think that the suggested method of adding "...AND Not UPGRADINGPRODUCTCODE" to the remove condition should be added to the documentation or mentioned in an InstallShield KB article on chained installers? 3. It appears that ISChainPackage fails when it needs to uninstall CHAIN_v1 (along with MAIN_v1) in the MAIN_v1 -> MAIN_v2 upgrade scenario and then install CHAIN_v1(or CHAIN_v1.1 with the same ProductCode) integrated into the MAIN_v2 installer. If the ProductCode of the chained installer changes, everything works fine. Do you think the same problem would occur if one populates MSIEmbeddedChainer and associated MSI tables instead of ISChainPackage/Data tables or this problem is indeed specific to the population of ISChain... tables and implementation of ISChain... custom actions? Thank you very much in advance for your reply!
... View more
Hello, I observe problems with a major upgrade in the following scenario: 1. I add a simplest Chained App MSI Package (created as Basic MSI ) to the simplest Main App (created as Basic MSI with MSI 4.5 prerequisite). This setup can be sucessfully installed on Windows XP SP2 test system. 2. Then I create a major upgrade of the Main App without changing anything in the chained MSI package. If I attempt to perform a major upgrade on the test system, the setup fails. Also changing PackageCode and version of the chained package and rebuilding the major upgrade of Main App does not solve the problem. Only if a chained installation is unistalled prior to performing a major upgrade, the setup gets accomplished successfully. 3. If I create a major upgrade of the chained installer and add this new msi (with a new product code) to the Main App installer, everything works correctly: the setup runs without problems and both appplications are upgraded. I have verified this behavior with simplest installers using IS 2009 and 2010. I have attached 2 installation log files created for the failed and successful installations. As can be seen in the failedsetup.log, the main app installer detects that the chained applciation with the same product code is installed and does not attempt to reinstall the chained installer. On the other hand, in case of sucessful setup the chained installer gets upgraded along with the main installer, if the product code of the chained installer differs from the one associated with the major upgrade. Can anybody explain the cause of the problem and suggest the method of its resolution? Thanks very much in advance!
... View more