MSI (c) (80:00) : Grabbed execution mutex. MSI (c) (80:00) : Client-side and UI is none or basic: Running entire install on the server.
******* Product: C:\WINDOWS\Installer\3dfeb63f.msi MSI (c) (80:00) : Machine policy value ‘Debug’ is 0 MSI (c) (80:00) : Resetting cached policy values 2435 Calling process: C:\Documents and Settings\User\Local Settings\Temp\SIT12330.tmp\setup.exe = = Verbose logging started: 14:26:48 Build type: SHIP UNICODE. This is because right before the action is run in the server context Windows Installer grabs the _MSIExecute mutex. That is, Windows Installer is processing the InstallExecuteSequence table, the AdminExecuteSequence table, or the AdvtExecuteSequence table, respectively. 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.
0 kommentar(er)
