Showing results for 
Show  only  | Search instead for 
Did you mean: 

InstallShield Repackager Hangs

By Level 11 Flexeran
Level 11 Flexeran
While packaging Outlook 2003 , the Repackager file (inc) hangs while building it. The screen displays Loading Registries and it does not proceed beyond. The total number of registries capruted is 9400. Is this teh reason why it hangs.
(4) Replies
I,ve never had a problem capturing many more registry entires than this.

But anyway !!!!STOP!!!! Office already comes as an MSI you should be creating a transform rather than repackaging it.

Here is a link to the special MS custom installation wizard for office -
I get the same freezing. I need to make a msi with all the files compressed in it rather than use the MS msi or a transform as suggested.
Does anyone have any suggestions on this?

I have an app with 2238 files. That's large but not outrageously so. I have not been able to build the ISM. Repackager v9 will stop at "Creating components for the files captured". I have left it running for over an hour, but no luck. It doesn't seem to be completely hung because I can click to cancel the build and it responds with "Cancelling... please wait". I have tried unchecking all of the Advanced Options including the merge modules, but no luck. Have also tried putting the captured files in a shallow folder so as to rule out problems with long path names. My host PC has plenty of horse power. Any one have an idea on this?
Hi All,

Some reasons why repackager might take a long time to build, or freeze during the process:

--Older versions of Repackager had a problem where more than ~10000 records (files, registry, *.ini files, etc.) would take a very long time. This has been fixed in the latest releases.

--For very long build times due to a high number of files, sometimes the issue has to do with querying the files on the disk in order to populate the File table. You can get around this by moving the *.irp, *.inc. etc. files to a different folder so that Repackager can't find the files, and then just build the *.ism file for use with InstallShield.

--For hanging on the Registry part of the build process, this can happen if invalid data makes it into the *.nir file. If this is the case, you would have to start slicing out parts of the *.nir file until the cause is evident (usually, it's excessively long binary data, or invalid characters in the key name). For the long binary values, this can happen when you're repackaging MSI's, and it's something that you'll usually want to exclude anyways (except perhaps in the case of Virtualization, since this will need to end up in *.context.msi).

Lastly, I should mention that there really isn't an easy way to get a single *.msi file for Office while still maintaining the best practices that ensure you don't break anything on the target machine. I might suggest creating a wrapper MSI file that uses the MSI 4.5 package chaining feature to push all the different packages one by one. I got about halfway through this a while back before getting redirected to another project, but it seemed to be doable with a bit of work. This approach would also have the advantage of maintaining patching compatibility with Microsoft Updates (since repackaging office would break this).

Hope this helps!