I'm using SCCM to deploy a MSI Shockwave (MSI with a MST to disable the 'Autoupdate' key in the registry) and I’m having trouble identifying why my Advertisement Status Logs is reporting the following Warning:


Windows Installer per-user elevation of this program ("xxxxxxxx" - " **program name** ")
failed for advertisement "xxxxxxxx". The operating system reported error 1618: Another installation is already in progress.
Complete that installation before proceeding with this install. This program was started.
Please check the status of this program to determine whether or not it was completed sucessfully
Possible causes: The version of Windows Installer on the computer is less than version 2.0, or the setup program
does not support Windows Installer per-user elevated rights installations.
Possible solutions: Update the version of Windows Installer on the computer to version 2.0 or later, or contact the
software vendor that supplied the install program to determine if a version of setup that supports per-user elevated rights
is available.

The command line in the program is the following;
msiexec /i sw_lic_full_installer.msi TRANSFORMS="MST\Adobe Shockwave Player 11.5.0.596 DoH.Mst" ALLUSERS=1 /qb!

The MST seems to apply correctly, and the application installs fine. I have confirmed the version of Windows installer is up to date and the MST is valid and using the correct source MSI file. The Program within the package has Run mode set to run with Administrator rights and Allow users to interact is also selected as I’m using the /qb! switch on the command line

I even used other VM's and they all seem to reproduce the same Warning in the Status logs.

Any help will be great.
Frank
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
The operating system reported error 1618: Another installation is already in progress.


Is there another installation in progress ?
Answered 05/06/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
Have you tried ALLUSERS=2?

IIRC ALLUSERS=1 checks to see if the installing user has admin rights and fails if it doesn't where as ALLUSERS=2 checks to see if installing user had admin rights, but installs for currently logged on user if it doesn't (no failure). You said the application installed anyways, so maybe this option gets rid of the error and you can go about your merry way :)

- J
Answered 05/06/2009 by: jcarri06
Senior Purple Belt

Please log in to comment
0
ORIGINAL: jcarri06

Have you tried ALLUSERS=2?

IIRC ALLUSERS=1 checks to see if the installing user has admin rights and fails if it doesn't where as ALLUSERS=2 checks to see if installing user had admin rights, but installs for currently logged on user if it doesn't (no failure). You said the application installed anyways, so maybe this option gets rid of the error and you can go about your merry way :)

- J


Yes i have tried this switch along with /qn along other different combinationa that are available in the Program Property Tabs in SCCM.

I discovered something really interesting thou. I installed another application with a MST file (which has passed testing and is in Production) and it produced same Warning in the Status logs when it didn't during its testing. So i thought maybe my VM developed a bug, so i reverted back to an old snapshot VM and it also produced the Warning.

So i tried it on another PC and that also developed the Warning for both applications i tested.

I don't know what it could be...
Answered 05/06/2009 by: hks7mgt
Senior Yellow Belt

Please log in to comment
0
Do you got the below registry key present?
HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress

In that case this would produce the "Another installation is already in progress" warning.
The key will be removed after msiexec has finished with its actions however; if something went very wrong during the msiexec "tasks" and crasched or the computer was ex. forced to be shutdown during this event the key could be left alone and therefore prevent any (new) msiexec "tasks".
Answered 05/07/2009 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity