I am trying to repackage a vendor installation (FileNet Panagon IDM Desktop 3.3 + hotfix to be exact) and I am able to successfully capture and create an MSI of the installation. However, when I convert my one and only feature ("Complete") to an MSM, it seems as though Windows Installer decides that it no longer needs to create all the registry keys when I use the merge module.

I have used Orca to determine that all of the registry keys made it to the registry table in both the MSI and MSM, yet when I install a package that contains only the MSM, I'm missing about 2500 of 9000 registry keys and things don't work so well! The vast majority of the keys are stuff from HKEY_CLASSES_ROOT and I can't see anything unusual about them by looking at the registry table data.

I am looking for any ideas as to why my registry keys might be getting whacked when I try to use my merge module.

I am developing on/for Windows 2000 SP3 using Wise Package Studio Professional 5.6. I used Wise for Windows Installer to create the merge module.

0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Why are you converting the capture to an MSM?

Use the capture as is and it should install all of the keys you require.
Answered 07/02/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment
I need to merge the FileNet application into a larger, custom application installation. A merge module seemed like the most logical way to go. At this point, I am reduced to calling the MSI from my main installation, which works, but I think that is going to complicate things like deinstallation. Is there some reason why I should avoid creating my own merge modules? (other than the fact that it doesn't seem to work!) [&:]
Answered 07/03/2005 by: BiffStorm
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity