Failed to grab execution mutex. System error 258
Hi All,
I'm trying to install an msi setup file. This msi installs my application which is an Excel based client. To run the client, I need VSTO. So I added the vsto exe in the setup project and added a custom action to install the exe on msi commit condition.
However, it throws the following error in the msi log:
=======================
MSI HEADER INFORMATION:
=======================
=== Verbose logging started: 12/31/2008 12:04:16 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: d:\b9a239c38a54294bb47c\install.exe ===
MSI (c) (2C:3C) [12:04:16:394]: Resetting cached policy values
MSI (c) (2C:3C) [12:04:16:394]: Machine policy value 'Debug' is 0
MSI (c) (2C:3C) [12:04:16:394]: ******* RunEngine:
******* Product: d:\b9a239c38a54294bb47c\vsto.msi
******* Action:
******* CommandLine: **********
MSI (c) (2C:3C) [12:04:16:394]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (2C:3C) [12:04:19:394]: Failed to grab execution mutex. System error 258.
MSI (c) (2C:3C) [12:04:19:394]: Cloaking enabled.
MSI (c) (2C:3C) [12:04:19:394]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (2C:3C) [12:04:19:394]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (2C:3C) [12:04:19:409]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (2C:3C) [12:04:19:409]: MainEngineThread is returning 1618
=== Verbose logging stopped: 12/31/2008 12:04:19 ===
========================
MSI COMPONENT LIST INFO:
========================
=======================
MSI FOOTER INFORMATION:
=======================
Any help?
Thanks,
Vishal
I'm trying to install an msi setup file. This msi installs my application which is an Excel based client. To run the client, I need VSTO. So I added the vsto exe in the setup project and added a custom action to install the exe on msi commit condition.
However, it throws the following error in the msi log:
=======================
MSI HEADER INFORMATION:
=======================
=== Verbose logging started: 12/31/2008 12:04:16 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: d:\b9a239c38a54294bb47c\install.exe ===
MSI (c) (2C:3C) [12:04:16:394]: Resetting cached policy values
MSI (c) (2C:3C) [12:04:16:394]: Machine policy value 'Debug' is 0
MSI (c) (2C:3C) [12:04:16:394]: ******* RunEngine:
******* Product: d:\b9a239c38a54294bb47c\vsto.msi
******* Action:
******* CommandLine: **********
MSI (c) (2C:3C) [12:04:16:394]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (2C:3C) [12:04:19:394]: Failed to grab execution mutex. System error 258.
MSI (c) (2C:3C) [12:04:19:394]: Cloaking enabled.
MSI (c) (2C:3C) [12:04:19:394]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (2C:3C) [12:04:19:394]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (2C:3C) [12:04:19:409]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (2C:3C) [12:04:19:409]: MainEngineThread is returning 1618
=== Verbose logging stopped: 12/31/2008 12:04:19 ===
========================
MSI COMPONENT LIST INFO:
========================
=======================
MSI FOOTER INFORMATION:
=======================
Any help?
Thanks,
Vishal
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
As ever, use the tools laready at your disposal: http://itninja.com/question/help-with-msi-1618
You cannot run an MSI installation (and VSTO is clearly extracting an MSI and running it) inside another MSI. You need to either create a wrapper for both MSIs or use some other method to deploay VSTO as a dependency. You may then want to add an AppSearch and LaunchCondition to detect VSTO before proceeding, if your package doesn't already do so.
You cannot run an MSI installation (and VSTO is clearly extracting an MSI and running it) inside another MSI. You need to either create a wrapper for both MSIs or use some other method to deploay VSTO as a dependency. You may then want to add an AppSearch and LaunchCondition to detect VSTO before proceeding, if your package doesn't already do so.
Posted by:
vishalchowdhary
15 years ago
I don't know how I can create this wrapper. Is there any easy and quick way to do so. I'm doing this just for the purpose of a small demo.
Posted by:
anonymous_9363
15 years ago
I don't know how I can create this wrapper.Why not reach for it, throw caution to the wind and use AppDeploy's Search function?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.