{"id":2533,"date":"2006-01-23T17:24:00","date_gmt":"2006-01-23T17:24:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/heaths\/2006\/01\/23\/waiting-to-install\/"},"modified":"2006-01-23T17:24:00","modified_gmt":"2006-01-23T17:24:00","slug":"waiting-to-install","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/setup\/waiting-to-install\/","title":{"rendered":"Waiting to Install"},"content":{"rendered":"

If you’ve ever tried to install a Windows Installer package and had returned ERROR_INSTALL_ALREADY_RUNNING<\/code> (1618) it’s because the Windows Installer execution server is already processing another install, administrative install, or advertisement action. That is, Windows Installer is processing the InstallExecuteSequence table<\/a>, the AdminExecuteSequence table<\/a>, or the AdvtExecuteSequence table<\/a>, respectively. This is because right before the action is run in the server context Windows Installer grabs the _MSIExecute mutex<\/a>. Take a look at the log below:<\/p>\n

=== Verbose logging started: 10\/3\/2005 14:26:48 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\\Documents and Settings\\User\\Local Settings\\Temp\\SIT12330.tmp\\setup.exe ===
\nMSI (c) (80:00) [14:26:48:285]: Resetting cached policy values
\nMSI (c) (80:00) [14:26:48:285]: Machine policy value ‘Debug’ is 0
\nMSI (c) (80:00) [14:26:48:285]: ******* RunEngine:
\n ******* Product: C:\\WINDOWS\\Installer\\3dfeb63f.msi
\n ******* Action:
\n ******* CommandLine: **********
\nMSI (c) (80:00) [14:26:48:285]: Client-side and UI is none or basic: Running entire install on the server.
\nMSI (c) (80:00) [14:26:48:285]: Grabbed execution mutex.<\/span>
\nMSI (c) (80:00) [14:26:48:295]: Cloaking enabled.
\nMSI (c) (80:00) [14:26:48:295]: Attempting to enable all disabled priveleges before calling Install on Server
\nMSI (c) (80:00) [14:26:48:295]: Incrementing counter to disable shutdown. Counter after increment: 0
\nMSI (s) (3C:1C) [14:26:48:315]: Grabbed execution mutex.
\nMSI (s) (3C:0C) [14:26:48:315]: Resetting cached policy values
\nMSI (s) (3C:0C) [14:26:48:315]: Machine policy value ‘Debug’ is 0
\nMSI (s) (3C:0C) [14:26:48:315]: ******* RunEngine:
\n ******* Product: C:\\WINDOWS\\Installer\\3dfeb63f.msi
\n ******* Action:
\n ******* CommandLine: **********
\nMSI (s) (3C:0C) [14:26:48:315]: Machine policy value ‘DisableUserInstalls’ is 0
\n…<\/p>\n

Multiple installer sessions can run in the client context concurrently but only one can enter the server context. If a concurrent installer session attempts to grab the execution mutex when another thread owns it, ERROR_INSTALL_ALREADY_RUNNING<\/code> is returned. This isn’t always desirable in automated testing. SMS could be installing something at the time, for example, and the install you’re intending to test will fail.<\/p>\n

Since mutexes are owned by a single thread, we can wait to own the mutex and then kick off an install successfully since the client will grab the execution mutex on the same thread if we’re making calls to Windows Installer APIs like the MsiInstallProduct<\/code> function<\/a>. Let’s take a look at some sample code that waits on the mutex and calls MsiInstallProduct<\/code> which can do just about everything you need from installing a new package to patching, and administrative installs to advertised installs.<\/p>\n

#define<\/span> WIN32_LEAN_AND_MEAN\n#include<\/span> <stdio.h><\/span>\n#include<\/span> <tchar.h>\n<\/span>#include<\/span> <windows.h>\n<\/span>#include<\/span> <msi.h>\n<\/span>#include<\/span> <string>\n<\/span>\ntypedef<\/span> std::basic_string<TCHAR> tstring;\n#pragma comment<\/span>(lib<\/span>, \"msi.lib\"<\/span>)\nint<\/span> _tmain(int<\/span> argc, _TCHAR* argv[])\n{\n  DWORD dwError = NOERROR;\n  LPTSTR pszPackage = NULL;\n  tstring strArgs;\n  HANDLE hMutex = NULL;\n  SECURITY_ATTRIBUTES sa = { sizeof<\/span>(SECURITY_ATTRIBUTES) };\n  \/\/ Make sure at least a package was specified.\n<\/span>  if<\/span> (2 > argc)\n  {\n    _ftprintf(stderr,\n      TEXT(\"Error: you must provide the path to a Windows Installer package.\\n\"<\/span>));\n    _ftprintf(stderr, TEXT(\"Usage: %s <package> [Windows Installer options]\\n\"<\/span>),\n      argv[0]);\n    return<\/span> ERROR_INVALID_PARAMETER;\n  }\n  \/\/ Get the path the specified package.\n<\/span>  pszPackage = argv[1];\n  \/\/ Build up remaining options as a single string.\n<\/span>  for<\/span> (int<\/span> i = 2; i < argc; i++)\n  {\n    strArgs += argv[i];\n    strArgs += TEXT(\" \"<\/span>);\n  }\n  \/\/ Grab the execution mutex when made available.\n<\/span>  hMutex = CreateMutex(&sa, FALSE, TEXT(\"_MSIExecute\"<\/span>));\n  if<\/span> (!hMutex)\n  {\n    dwError = GetLastError();\n    _ftprintf(stderr,\n      TEXT(\"Error: failed to grab execution mutex. GetLastError() = %d\\n\"<\/span>),\n      dwError);\n    return<\/span> dwError;\n  }\n  \/\/ Wait to grab ownership of the execution mutex.\n<\/span>  _tprintf(TEXT(\"Waiting for execution mutex...\\n\"<\/span>));\n  dwError = WaitForSingleObject(hMutex, INFINITE);\n  if<\/span> (WAIT_OBJECT_0 == dwError)\n  {\n    \/\/ Install the package on the current thread owning the execution mutex.\n<\/span>    _tprintf(TEXT(\"Installing the specified package...\"<\/span>));\n    dwError = MsiInstallProduct(pszPackage, strArgs.c_str());\n    _tprintf(TEXT(\"done.\\n\"<\/span>));\n  }\n  if (ERROR_SUCCESS != dwError)\n  {\n    _ftprintf(stderr, TEXT(\"Error: an error has occured. GetLastError() = %d\\n\"<\/span>),\n      dwError);\n  }\n  CloseHandle(hMutex);\n  return static_cast<\/span><int<\/span>>(dwError);\n}<\/pre>\n
Now even if another installation is being processed in the server context we can wait to install whatever product we specify by using a command similar to the following. Assume the code was compiled to MsiWait.exe<\/i>.<\/p>\n
MsiWait.exe Package.msi ACTION=INSTALL<\/p>\n","protected":false},"excerpt":{"rendered":"
If you’ve ever tried to install a Windows Installer package and had returned ERROR_INSTALL_ALREADY_RUNNING (1618) it’s because the Windows Installer execution server is already processing another install, administrative install, or advertisement action. That is, Windows Installer is processing the InstallExecuteSequence table, the AdminExecuteSequence table, or the AdvtExecuteSequence table, respectively. This is because right before the […]<\/p>\n","protected":false},"author":389,"featured_media":3843,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[20],"class_list":["post-2533","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-installation"],"acf":[],"blog_post_summary":"
If you’ve ever tried to install a Windows Installer package and had returned ERROR_INSTALL_ALREADY_RUNNING (1618) it’s because the Windows Installer execution server is already processing another install, administrative install, or advertisement action. That is, Windows Installer is processing the InstallExecuteSequence table, the AdminExecuteSequence table, or the AdvtExecuteSequence table, respectively. This is because right before the […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/2533","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/users\/389"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/comments?post=2533"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/2533\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media\/3843"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media?parent=2533"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/categories?post=2533"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/tags?post=2533"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}