Related product shows "not related" during major upgrade

[PilotBob]

Can anyone tell me what might be happening here. I have major upgrade authored, I have verified the .msi of the previous version and it seems to have the same upgrade code, language and ALLUSERS setting... here is the log:


InstallShield 19:41:19: UpgradeCode: {BCAAAA51-B350-4B0C-B5C3-2EE2F04A9ECE} MinVersion:
1.0.0 MaxVersion: 7.0.0 Language:
Attributes: 1
MSI (c) (1C!84) [19:41:19:800]: Closing MSIHANDLE (7) of type 790531 for thread 3972
MSI (c) (1C!84) [19:41:19:800]: Creating MSIHANDLE (8) of type 790531 for thread 3972
InstallShield 19:41:19: Checking related product {AD42CFE3-9D81-4853-9020-1BB9054FFD1C}
MSI (c) (1C!84) [19:41:19:801]: Closing MSIHANDLE (8) of type 790531 for thread 3972
MSI (c) (1C!84) [19:41:19:801]: Creating MSIHANDLE (9) of type 790531 for thread 3972
InstallShield 19:41:19: AMSI Property Management {AD42CFE3-9D81-4853-9020-1BB9054FFD1C} 1033 6.5.3 ***Not Related***


WHat else can I check?

BOb

[Alpesh]

Hi,

Check if the previous version was installed as per-user or per-machine? And then check the current msi's ALLUSERS property value. The context in which the install happens, has to be the same for the Major Upgrade to work.

Thanks!

[PilotBob]

Thanks... I have looked at the previous installs msi, and ALLUSERS is set to 1. I provide no way to change it. I've done that install myself on my test machine... so it certainly is a per-machine installed.

My new version also has ALLUSERS set to 1 so it is doing a per machine install.

This is quite frustrating. I spent 4 hours on this one issue and am just about ready to surrender and tell the customers to just manually uninstall the old version first. But, that just looks so unprofessional to me.

BOb

[PilotBob]

Could it be because it is signed and the previous installer wasn't?

BOb

[PilotBob]

It seems the issue was due to the language not being set in the Upgrade item. I have never had to set that before. I set it to 1033 and the log now shows the previous install is related.

One thing though, I have it set to do Full Uninstall prior to installing the new version... that doesn't seem to be happening.

What would cause it not to do the full uninstall of a previous version first?

Thanks,
BOb

[PilotBob]

It does seem to be doing the full remove first... but it is not putting files back. If I do a repair install they get added. I thought the whole reason to do "full uninstall first" was to avoid funky issues like this.

This is very frustrating. Any ideas how to resolve this?

BOb

[Poltron]

I had a problem like this where the major upgrade was uninstalling prerequisites and not fully installing them, leaving me with a broken machine.

😞

We changed to handling the major upgrade ourselves. In the upgrade table we have an entry for:

MAJORUPGRADE_DETECTION with the advanced tab settings:
Upgrade Code: {00000000-0000-0000-0000-000000000000}
Detect Property: MAJORUPGRADEGUID

Then a custom action:
MSI CA type number: 98
working dir: SystemFolder
Filename & Command line msiexec.exe /x[MAJORUPGRADEGUID] /qb /passive

Then we call this from the custom action "Install" button in the UI Sequence. Doesn't work for silent installs and we have another CA to abort major upgrades if it's a silent install.

Not a perfect solution, but it's been working for the last 2 years.