Hi, I am packaging a Wise .msi which I need to create an upgrade for. I opened the .msi with IS2013 SP1 to create an .ism. The .ism won't build error-free, though it produces a .msi. I have run validation on the created msi with ORCA, and fixed m...
I'm running Admin Studio 2013 R2 Repackager remotely. I'm trying to get it to skip the installation monitoring step and just build the ism and msi. My command line is:\\Server\RepkgShare$\repack.exe -b "path where ism should be created" -o "path to ....
Output of validation run from ORCA on the built msi: Is there anything here serious enough to cause a build error?ICE03 ERROR Invalid filename/usage of wildcards; Table: RemoveFile, Column: FileName, Key(s): RemoveFileICE03 ERROR Invalid filename/us...
Not sure what I'm doing differently from you, but it is still not working. I read the KB, and it's the same info you gave me. I used the new options, in the same order.It may have something to do with the way I'm running repack remotely. How do yo...
Thanks for your reply and suggestion, Alpesh, but it produced the same results.Here's the command line from my batchfile:\\server\Repackager$\Repack.exe -aacb "C:\Packages\%ProdFolder%\Workspace\%ISMName%" -o "C:\Packages\%ProdFolder%\Workspace" -pp ...
I think the problem is that Repack (the Wizard) can't launch Islc.exe (the Repackager) remotely, which is what does the building. When the Wizard gets to its Summary screen and I click Finish, the Repackager doesn't launch; the Wizard just quits.Whe...
.NET is not a prerequisite for installations in general. You say that your installer includes 2 versions of .NET. I would guess that when your installer attempts to install one of them, it recognizes that the target's .NET is corrupt and raises the...
