InstallShield 2016 : Failed to grab execution mutex 258 while running multiple exe's. Chaining issue

[devflex]

Dear members of the community, here is my issue:- 

I have an InstallShield 2010 project (InstallScript project) that was converted to IS 2016.

The setup exe has to install database and client components via calling separate exes.

On launching the exe I am able to see the DB installation start but immediately it attempts to start off the Client installation and gives the "Installation Finish" screen (while DB installation is still in progress - I can see the dialog box with progress bar but still the installation finish screen is displayed). 

I am able to see in the Client installer log error as : "Failed to grab execution mutex 258" which means it is trying to access some resource that is still being accessed by the DB installation. 

When I'm running the same exe by selecting the installation component separately (from the installation binary tree options) it is able to install both the components correctly. I am able to launch the application fine. It is failing when it is expected to launch and install both exe's concurrently - one after the another - a concept that is called MSI chaining. 

The Setup exe was functioning correctly with the previous version of InstallShiled, i.e 2010. The issue came after we migration to IS 2016. 

Any help would be greatly appreciated. 

[banna_k]

Hi @devflex ,

See whether your issue can be solved by specifying clone_wait parameter for the prerequisite setups

https://community.flexera.com/t5/InstallShield-Knowledge/Installer-Does-Not-Wait-For-Child-Process-To-Finish/ta-p/4202

Let me know, How you created the  install database and client components setup exes, if it is generated out of installshield, you can try clone_wait parameter 

 If database and client components setup exes are configured in the installshield prerequisites, then you can edit the prerequisite(from the context menu) and add the clone_wait parameter under "Application to run" tab.

[devflex · Accepted solution]

The issue was due to a parameter that was updated in InstallShield 2016 SP1 edition. Here is the link: https://community.flexera.com/t5/InstallShield-Knowledge/LaunchAppAndWait-nOptions-Parameter-When-Using-InstallShield/ta-p/4302

Adding the suggested parameter solved the issue for me.