This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Merge module not installing during upgrade
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 06, 2009
03:31 PM
Merge module not installing during upgrade
We have a current product out in the field version 4.30.
We are working on our new version 4.40 which now has a new set of merge modules for Crystal Reports version 11.5.
The version 4.30 did not have any merge modules in it. If I run the version 4.40 install as a new instance it will install the crystal reports merge modules. But if I run it as an upgrade over a previous 4.30 install the merge modules do not install. I have tried to create a new feature for just the merge modules and selecting that feature in the code to force the install but that did not work as they still did not install.
How can I force the merge modules to launch and install?
We are working on our new version 4.40 which now has a new set of merge modules for Crystal Reports version 11.5.
The version 4.30 did not have any merge modules in it. If I run the version 4.40 install as a new instance it will install the crystal reports merge modules. But if I run it as an upgrade over a previous 4.30 install the merge modules do not install. I have tried to create a new feature for just the merge modules and selecting that feature in the code to force the install but that did not work as they still did not install.
How can I force the merge modules to launch and install?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 07, 2009
07:54 AM
Once a merge module is merged in, it is just another set of components to the MSI.
Are you running your upgrade as a minor upgrade? If so, you are essentially doing a reinstall, and MigrateFeatureStates by default will only reinstall the components that are already there. You may have to experiment with setting ADDLOCAL to force the reinstall to install additional components. (Or you might be able to mark the new feature as "required" by a feature that you know is installed. I haven't done that, but I believe I've read about others doing it.)
Are you running your upgrade as a minor upgrade? If so, you are essentially doing a reinstall, and MigrateFeatureStates by default will only reinstall the components that are already there. You may have to experiment with setting ADDLOCAL to force the reinstall to install additional components. (Or you might be able to mark the new feature as "required" by a feature that you know is installed. I haven't done that, but I believe I've read about others doing it.)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 07, 2009
12:24 PM
I forgot to say we are using installscript and not MSI windows installer. I will try the required option and see if that does the trick.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 10, 2009
09:21 AM
Hi, can you post if this solution helped at all, I have the same problem, or if there is another solution to this problem:
http://community.acresso.com/showthread.php?p=443280#post443280
http://community.acresso.com/showthread.php?p=443280#post443280
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)