This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Main MSI installer not waiting for inner MSI to complete
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 25, 2013
12:50 PM
Main MSI installer not waiting for inner MSI to complete
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.
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.
- Tags:
- custom action
- msi
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 27, 2013
03:23 PM
Creating nest/concurrent installations is deprecated by Microsoft. Instead perhaps consider using a chained MSI, suite project (if you have Premier) or an Installscript wrapper.
If you must create a nested installer, however, I suggest taking a look at the following kb article which contains additional steps and information: http://flexerasoftware.force.com/ka2G0000000UFLnIAO
If you must create a nested installer, however, I suggest taking a look at the following kb article which contains additional steps and information: http://flexerasoftware.force.com/ka2G0000000UFLnIAO
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)