/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Extracted msi deployed from SCCM fails to install with error:1500

02/20/2020 647 views

Deployed MSI(extracted from setup.exe) from SCCM fails to install with error 1500: Another installation is in progress. You must complete that installation before continuing this one.

There are no other processes using windows installer. Manual install has no issues.

Can someone suggest please?


Answer Summary:
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

0

ZMi2P+hCAaIclvU92XKfe1I8aAIBohyC0lfptzXjhQPiiAhJNCEIkn8ajPfNkcICSgUQUJIoKEIEkICDccECSGBhiJICAk0oUgSz3U8TREkhASTUCSJ33RuoAgSQoJJKJLEb7ueoQgSQoJJKJLE77ZuxP8D1qDPhqsQsQoAAAAASUVORK5CYII=


according to these switches it is not recommended to exctract the MSI from this exe but to use the msi switches this exe provides which are /V (v has to be capital)
so for a silnet install it would be like .exe /S /V"etc...." 
you need to do a bit trial and error with this one as these kind of exe to msi switches can be funny.

also please do say next time the full vendor name and app coz google was being rude with only asoffice 2.0...

Answered 02/24/2020 by: haway_the_lads
Senior White Belt

  • Thanks a lot for your time and suggestions.
    I have got confirmation from Vendor that this software doesn't support SCCM deployment. It must be installed manually
    • cheers mate.
      BUT WHERE MA POINTS ATTTTT ?????? hehe ;p

All Answers

0

Well its not a lie! There probably was a install happening at that time. 

I would suggest you use the PowerShell App Deployment Toolkit, as this has in script features to check the MSI mutex, before trying to install the MSI - this should work around your issue.
https://psappdeploytoolkit.com/


Just to note, if you wait SCCM will retry the install itself, even without the PSDeploy above. Remember SCCM not a instant deployment tool.


Answered 02/21/2020 by: rileyz
Red Belt

  • Thanks for the response.
    Unfortunately, no other process is running. For testing, i have deployed other msi to the same machine which installed with no error. This package still has issue.
    Tried deploying Setup.exe and also extracted MSI , both gave same fail result.
    • Humm. Enable full logging with /l*vx
      so you can see whats going on during the install, might not help much tho, as that error is a standard msi error. Cant really tell you much without the logs.

      Are there any weird CA's that could impact it, unlikely but worth a look?
      • +1 to that. need to check logs anyway to determine next steps.
        could i have the setup / software name?
      • === Verbose logging started: 24/02/2020 12:31:02 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
        MSI (c) (68:10) [12:31:02:096]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

        MSI (c) (68:10) [12:31:02:096]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

        MSI (c) (68:E4) [12:31:02:135]: Resetting cached policy values
        MSI (c) (68:E4) [12:31:02:135]: Machine policy value 'Debug' is 0
        MSI (c) (68:E4) [12:31:02:135]: ******* RunEngine:
        ******* Product: C:\Windows\ccmcache\29\1cc695.msi
        ******* Action:
        ******* CommandLine: **********
        MSI (c) (68:E4) [12:31:02:136]: Client-side and UI is none or basic: Running entire install on the server.
        MSI (c) (68:E4) [12:31:05:136]: Failed to grab execution mutex. System error 258.
        MSI (c) (68:E4) [12:31:05:145]: Cloaking enabled.
        MSI (c) (68:E4) [12:31:05:145]: Attempting to enable all disabled privileges before calling Install on Server
        MSI (c) (68:E4) [12:31:05:148]: Incrementing counter to disable shutdown. Counter after increment: 0
        MSI (c) (68:E4) [12:31:05:149]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
        MSI (c) (68:E4) [12:31:05:150]: MainEngineThread is returning 1618
        === Verbose logging stopped: 24/02/2020 12:31:05 ===


        Log file has the above information. Application is asoffice version 2.0.9.7. Seems it installs in User context. SCCM deployment does in system context. Not sure if that is the reason for install failure
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ