I have an MSI created by another company which has been distributed to us as a setup.exe. I have tried everything other the sun to get this to install concurrently with my .msi with no luck. If I can only install this as a chained MSI package, then how do I chain this setup.exe to my .msi installer? Even though the setup.exe takes MSI paramaters, it still has the .exe extension which isn't allowed to be chained in InstallShield. Are there any work arounds at all to get this to install concurrently? This is for use within our organization, and therefore will not be distributed out to the public. ... View more

I have a problem that I have been stuck on for awhile. Basically I am creating an msi that, among other things, silently runs another exe (which itself is an msi) installer. My problem is, when my program runs this exe installer silently, it conflicts with my msi installer and errors out. To me it appears that since they were both created with InstallShield, the exe tries to execute but conflicts with my concurrently running msi and terminates. The reason I believe this is if I set the exe to install asynchrnously, the installation will silently install after my msi just fine. The problem with this is that we are going to deploy this MSI package using the Windows Deployment System and I fear that when my MSI terminates, WDS will be unaware that the exe is still executing in memory and cause problems. I want the exe to completely install itself within my msi. I have tried numerous execution methods in my custom action, but it all appears to come down to the fact that the exe will not play nicely with my msi if they try to concurrently execute. NOTE: I have tried waiting for an exit code from this exe as well with no luck. Any ideas? ... View more

So I have read quite a bit and tried multiple settings, however I cannot figure this out for the life of me. Basically I am running an inner installer within my msi silently using /s /v"/qn" switches. How I currently have it set up is that I drop the inner installer to the my destination folder, and then execute it during my installation. So in the Install Exec Sequence, I have it set to "After InstallFiles". Return processing is set to Asynchronous (No wait for completion). However, any other option other than Asyncronous (No wait for completion) fails. The installer will simply continue on and never run the inner msi unless that specific option in return processing is set. Obviously this is not what I want. I want my main installer to wait for the completion of the inner installer before proceeding. Currently it will start the inner installer, and then my msi will install concurrently with it. This causes problems as obviously I want to wait for the inner msi to finish before my installer does. In the end it works, and everything is deployed like it is supposed to be without conflict, but I fear this will cause problems when running this package through WDS. ... View more