New Inshallshield Patch does not get installed and rollback to a previous patch

[janzzen2011]

We have encountered a problem where a new patch that we built does not installed in certain scenarios, and could actually rollback to a previous version. The patch we are building is for our release E. The product version used for this patch is 18.10.3002. The following is our patch design.

Full Release A (18.00.1000)
Full Release B (18.00.2001)
Release B Patch (18.00.2002)
Full Release C (18.10.1001)
Release C Patch (18.10.1002)
Full Release D (18.10.2001)
Release D Patch (18.10.1202)
Full Release E (18.10.3001)


The weird thing is, the new patch only does not work when our clients have the following installed.

Full A + B patch + C patch + D patch + E patch ==> after installing E patch, we find that all the files are the same as C patch.

Full B + C patch + D patch + E patch ==> after installing E patch, we find that all the files are the same as D patch.

All other install configuration are fine. For example, Full B + C patch + E patch is fine. In the end, the files installed are correct.

Since the product version for E patch is 18.10.3002, it should work. However, it does not for two scenarios.

Has anyone encountered this, or have any suggestion on where/what to look for?

[Cary_R]

This certainly sounds strange. Can you post the logfile of patch E getting applied?

As well, can you post what each Patch GUID is? I believe if you open the *.msp file with Orca, or using Direct MSP mode in InstallShield, you can pull the GUID from the patch this way.

[janzzen2011]

Hi,

I have attached a portion of the log file. If you need more info from the log file, please let me know. As for the patch GUID, I do not have the msp file. So, I grab them from the log file.

Patch B: {A9EAF17E-0D2C-40A6-9D90-BAB0F5CBB06C}
Patch C: {CD77D751-45F8-4818-8309-C1CE44AA97BA}
Patch 😧 {95F62D36-4C24-4F64-B7E4-3AAA51B92DA6}
Patch E: {35E834A4-0332-431C-A664-8C3228C7A174}


Thanks,
Janz.

[Cary_R]

From the log, it's clear that Patch E ends up on top, and previous patches are superseded from the view.

I might recommend boiling down the investigation to a single file you can identify as coming from Patch C. Then, check that file's component in the 'InstallValidate' section to what the Action state is.

Lastly, look for a FileCopy operation in the Deferred section of the logfile to see what *.cab file it's pulling the file from. If you could also post the full log with the file and component name, I could review this and see if there's further clues there.

[janzzen2011]

Hi,

I have attached the full log. Thanks for your help.


Thanks,
Janz.

[janzzen2011]

seriously, no one else has this problem? 😞