InstallAware

Hello,

Our company's product is built into 3 different installer:
1. Platform
2. Module A
3. Module B

First installation works very well in following order: Platform v1.0 -> Module A v1.0 -> Module B v1.0

After that, I tried to upgrade Platform from v1.0 to v1.1. It worked well until the last minute before finish. The installer want to access the msi file of Module A. I can locate the msi file manually in C:\\ProgramData folder, and the installation will finish successfully. Otherwise, it will failed and left some invalid shortcut in start menu folder.

These 3 installers are completely seperated, and have different product code and revision code. Their MSI code are not related at all.

Could you help me to identify the cause of this strange problem? Thanks.

Hi Carlos,

It does sound like there is a shared entry here somewhere.

I would recommend building them as uncompressed installs, and using ORCA to check that the setups are not referencing each other for sure -- then would open a support ticket so we can check into your scripts.

Thanks for you instruction.

I tried ORCA, and found that msi files from two installer share the same UpgradeCode.

I also read a very similar scenario in the topic about UpgradeCode in http://msdn.microsoft.com/en-us/library ... 85%29.aspx .

Product A and Product B were shipped with the same ProductLanguage, ProductVersion, and UpgradeCode. Product A and Product B have different ProductCodes. Because the products were assigned the same UpgradeCode, the Upgrade table cannot be authored to differentiate the older version of Product A from the older version of Product B. In this case, you will be unable to have an upgrade installation of Product A that ignores Product B. Because these were different products, they should have each been assigned a different UpgradeCode.

Is this the cause of my problem? If it is the reason, is there way to fix it in installaware?

Thank you very much.

It's certainly not a good idea sharing the same upgradecode! I would advise changing this, and you should see the problem disappear

Cool, I manually changed UpgradeCode in "FINAL GENERIC.mpr". All fixed. Thank you very much.