not all upgrade scenarios are working

[TurboFisch]

I have 4 upgrade scenarios. Two of the these fail to completely install. The files are there but shortcuts are missing and dll registration appears to not have occurred. If I run repair, then the software works flawless.

What should I look for in the log?

AlllUsers indicates that is can find it:
InstallShield 13:35:59: Begin SetAllUsers()
InstallShield 13:35:59: Getting records from Upgrade table
InstallShield 13:35:59: UpgradeCode: {3C25E2CB-CEAD-11D3-BECE-0060B0A1E303} MinVersion: MaxVersion: 99.99.99.9999 Language: Attributes: 512
InstallShield 13:35:59: No related products for UpgradeCode {3C25E2CB-CEAD-11D3-BECE-0060B0A1E303} found
InstallShield 13:35:59: UpgradeCode: {3C25E2CB-CEAD-11D3-BECE-0060B0A1E303} MinVersion: 11.00.00 MaxVersion: 11.00.99 Language: Attributes: 768
InstallShield 13:35:59: No related products for UpgradeCode {3C25E2CB-CEAD-11D3-BECE-0060B0A1E303} found
InstallShield 13:35:59: UpgradeCode: {3C25E2CB-CEAD-11D3-BECE-0060B0A1E303} MinVersion: 12.69.19 MaxVersion: 99.99.99.9999 Language: Attributes: 769
InstallShield 13:35:59: No related products for UpgradeCode {3C25E2CB-CEAD-11D3-BECE-0060B0A1E303} found
InstallShield 13:35:59: UpgradeCode: {6A10DEF6-2C6E-4B6F-9CC8-9ECBE1A64D8E} MinVersion: 0.0.0.0 MaxVersion: 99.99.99.9999 Language: Attributes: 769
InstallShield 13:35:59: Checking related product {2F1BF1BA-417F-4BD2-B2A7-5D627EFC614A}
InstallShield 13:35:59: Really Good Software {2F1BF1BA-417F-4BD2-B2A7-5D627EFC614A} 1033 10.56.09.301.0 ***Related***
MSI (c) (18!4C) [13:35:59:289]: PROPERTY CHANGE: Adding IS_MAJOR_UPGRADE property. Its value is 'Yes'.
InstallShield 13:35:59: ALLUSERS of related product {2F1BF1BA-417F-4BD2-B2A7-5D627EFC614A} is = 1
InstallShield 13:35:59: End SetAllUsers()

Any help would be appreciated, thanks

[sdnelson]

What are the conditions on the custom actions or components that are sometimes not installing properly, and which upgrade mode are they not working in?

[TurboFisch]

the INSTALLDIR is different, as our company changed name
the old version has a single shortcut to the application
the new version has shortcuts based on the feature, some have a launcher instead of calling the application directly
registration is still in ISelfReg table, that has not change, but dll's appear to be unregistered when upgrading

features gets enabled based on a condition. this sets the INSTALLEVEL to a higher value.
old version did not have conditions like that.

thanks,

[sdnelson]

Changing the INSTALLDIR value shouldn't matter.

Please explain what the 4 scenarios are. Is it Major Upgrade, Minor Upgrade, New install, and Patch? Which 2 are the ones not working?

In your log snippet, you are running a Major Upgrade. Are the files getting successfully Un-registered during the removal of the old build? If not, maybe that is preventing the installation of the new build from registering the same files?

During installation of the new build, do you get an error message when the self-registration fails?