Remote Repackager Problems (AS10)

[ds0934]

We are having an intermittent issue with the Repackager output when using Remote Repackager and opening the output ISM in InstallShield Editor. The problem is that some files will fail to resolve saying they can't be found in "C:\Packages", which appears to be hard-coded in the IRP. The frustrating aspect is that it's never all of the files, only a few, and that it only happens once in a while. Is there some place we can check (prior to InstallShield) to see where it's hard-coding the source path instead of using a reference variable?

We are using AdminStudio 10 SP2 on Windows 7 64-bit SP1 (physical installs) and running the Remote Repackager within a VMware Workstation guest machine built with Windows 7 32-bit SP1.

Our best guess is that this issue occurs about once in every five repackage processes. The only workaround we've found thus far is to copy the source binaries to a C:\Packages folder, then InstallShield can open the ISM without errors.

[Darwin1]

When you create the repack, it asks where you want to save the output. Default is c:\packages.

It then tries to open the files from there, when you build the package from ism. It's normal. It has to know where the necessary files are.

Best practices, in my humble opinion, is to put the output in a shared path in the network. If you do so, you normalize all the installation processes, you can have more than one technician working, and you avoid loosing your work if you forget to copy the files and format/clean the machine. You do you use virtual machines or clean ones in the repack process, right? 🙂