ISSetupFilesExtract fails after upgrading to 2013
Posted 26 June 2014 - 11:11
Posted 27 June 2014 - 06:25
Why on earth are you extracting MsiZap.exe? If you are using this to zap an existing installation your setup is so dangerous that it will certainly be facing shutdown along the lines of what the log shows. What exactly are you doing?
Posted 27 June 2014 - 10:03
Posted 27 June 2014 - 17:24
MsiZap is not reliable in newer versions of Windows. It is very likely the culprit of the problem you are seeing as it may cause strange errors that are hard to predict and affect the whole system or its ability to install via Windows Installer at all.
I know you will likely try to keep this "solution", but I will have to refrain from answering any follow-up questions on this tool since I am very much against its use in the first place. The only sane solution is to remove this tool and rebuild your setup to see if the problem disappears. Test on a clean system.
The leaked handles relate to problems with the table and view for the database. A simple quick test could be to do a "Save As..." on the MSI database and then compile a new build. A "save as" operation will write all streams in sequence, and could hence fix any corruption in the original MSI file, but I doubt it. It sort of just defragments the MSI file (or ISM as Installshield calls them - they are really MSI formatted files).
Edited by Glytzhkof, 27 June 2014 - 17:36.
Posted 30 June 2014 - 07:53
Try running Process Monitor (from Microsoft SysInternals) to get more information about the problem. It might no be with MsiZap but with the next setup file it's trying to extract. Anti virus blocking the extraction? You say it's failing only on one nachine, so it may not be InstallShield 2013's fault but something special on that machine, or a combination of both.
Posted 30 June 2014 - 10:06
Posted 30 June 2014 - 21:07
I am going to try to mention a few "under the hood" type of fixes for this issue. I provide no guarantees for this, try at your own risk. You need a solid backup before you try any of this.
- You can probably "fix" the problem by deleting all support view files and re-add them. This may yield several broken file paths though. I can't recall exactly, and I don't have Installshield available at the moment.
- You could also open the ISM file with Orca and delete the content from the ISSetupFile table directly. When re-adding files to the support view using Installshield afterwards it should re-generate the ISSetupFile table. I have seen some really strange errors at times relating to ISM files that have been through upgrading. The _Validation table has played a role in some of them.
- For problematic ISM files I have used Orca to delete several Installshield specific tables and then have them re-created by opening the file in the newest version of Installshield.
Posted 01 July 2014 - 09:53