I have a setup.exe...and an MSI.

In my first attempt I thought this was going to be simple...extract the ISsetup11.msi and pass via MST to my MSI the property ISSETUPDRIVEN=1. When I goto install the product (after installing ISsetup11.msi) using msiexec /i "CS Webpublisher PRO.msi" TRANSFORMS="CS Webpublisher PRO.mst" (I am not testing quiet though) it extracts and then fails on ISCleanupFiles...commenting out ISCleanupFIles causes the MSI to fail entirely. Debug even crashes when I try to troubleshoot.

On my second attempt for giggles I tried a flat out installation to the harddrive and capture creating my own MSI. It fails on an IE check, however there are no System Requirements set under Windows Installer Editor. I am unable to find/edit/remove the "invisible" IE check. I even forced a reg hack on Windows to make sure the keys checked were "true".

Finally I've tried to perform a iss record....setup.exe /r, after it went completely through I pulled out the setup.iss and ran the following all from the same directory setup.exe /s /f1"setup.iss" and it passes through the setup.exe and visibly runs the MSI with nothing passed to it.

Any guidance is appreciated.
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.


Hi Timothy,
ISCleanupFiles is used to remove helper files installed to the temp folder (in a subfolder named after the [ProductCode]). Please make sure that you have sufficient privileges to remove files on the temp folder. You can see the helper files by opening the MSI in ORCA and check the 'ISSetupFile' table.
Also log the install and post the lines around the error.
And here some interesting stuff, that could maybe be of some help:
Regards, Nick
Answered 05/06/2007 by: nheim
Tenth Degree Black Belt

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