We have created a minor upgrade using msi 3.1, where new components were added. We are using one patch family that has one latest build and multiple previous builds. The patch installs all the new components when it is applied to the immediate previous version. When the patch is applied to previous version that are further back then the components that were added between these releases are not installed. If you manually run a repair on the product then the components are installed. For example, version 1.0 installs component a, version 1.1 installs components a and b, version 1.2 installs components a, b and c and version 1.3 installs components a, b, c and d. We create a single patch to upgrade to 1.3 that will patch 1.0, 1.1, and 1.2. If we apply the patch to version 1.2 then component d is added. but if we apply the patch to 1.1 then component c is not installed. If we apply the patch to 1.0 then components b, and c are not installed. The key files for these components are non-versioned files and do have entries in the msiFileHash table. We are using installshield 12 to produce the msi and msp files. We have resorted to creating seperate patch families for each version which is a nightmare. Anyone have any suggestions.
Thanks,
Damien
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Patch does not install new files
Started by
dmurty
, Mar 27 2008 00:36
3 replies to this topic
felltier-a
-
- Awaiting Authorisation
- 85 posts
Posted 27 March 2008 - 07:21
| QUOTE |
| If you manually run a repair on the product then the components are installed. |
seems to me that the features are not reinstalled during the patch. Have you set "REINSTALL" and "REINSTALLMODE" property?
You can try to pass the properties as command line argument.
for example:
REINSTALL=ALL REINSTALLMODE=omus
dmurty
-
- Full Members
- 5 posts
Posted 27 March 2008 - 15:31
I have it set so that the update.exe that installshield builds sets the following parameters for msiexec.exe:
REINSTALLMODE=omus REINSTALL=ALL
But I will try explicitly running the msiexec command to see if maybe it is something wrong with the update.exe that installshield is building.
Thanks,
REINSTALLMODE=omus REINSTALL=ALL
But I will try explicitly running the msiexec command to see if maybe it is something wrong with the update.exe that installshield is building.
Thanks,
dmurty
-
- Full Members
- 5 posts
Posted 27 March 2008 - 21:00
Figured it out with a lit trial and error. The documentation from InstallShield does not do a good job with explaining the purpose of the settings. Anyways the issue was when you include multiple previous version you need to change the Transform filter so that the version relationship is set to Previous Setup Version = Latest Setup Version. The default is Previous Setup Version <= Latest Setup Version and is under an advanced tab for each previous version added to the patch.
Hope this helps anyone else that has had this issue.
Thanks,
Hope this helps anyone else that has had this issue.
Thanks,