I'm trying to automate an installshield .exe which calls a .msi. If I attempt to launch the .msi, an error message is generated indictating the setup.exe must be launched to continue the installation. Is there a way to go around this issue?

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Depends, there are a couple of things I can think of to try.

1) Rip out the custom actions / properties etc which are insisting on setup.exe (It took a little time but I managed to get this working with Quicktime 7 setup the other day)

2) Try creating an admin install from setup.exe - think the switch to pass parameters to msiexec is /v so it would be "setup.exe /v /a" (type setup.exe /? to see if it's supported). However you may find that the resulting MSI still asks for setup.exe..

If you can't get around the setup.exe thing then I'd try snapping the install and removing all the installshield crud from your capture. I can't stand installshield setups - grrrrrr [;)]

Good luck,
Answered 10/21/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
Add the ISSETUPDRIVEN property and give this new property the value 1.[;)]
Answered 10/21/2005 by: Ledge
Senior Yellow Belt

Please log in to comment