Handling "Server Locked: Install is suspended for product" (Error 1704)

[bdampmpc]

Recently we had a report that our installer was triggering an unexpected reboot. Digging into it, it looks like a previous install of Adobe ... always Adobe ... was suspended. It appears that it's suspended because there's in-use files and has flagged that a reboot is needed (MsiSystemRebootPending = 1). The default behavior of our installer seems to be to 'undo those' changes whereby it starts uninstalling Adobe's files and registry entries and exits with a 1604 which triggers a reboot.

Since we see MsiSystemRebootPending = 1, I think we should be able to enable the “Prevent running if pending system changes that require a reboot is detected” launch condition but we worry that will create more issues than it fixes. When apps are delivered via things like ConfigMgr/SCCM or Intune, multiple MSIs might be installed and we'd rather not fail our installer if one of them needs a reboot.

In the log, you see it asking us if we want to undo the other app's changes (Adobe). The default appears to be 'yes, is there a way to default that to 'no' when ran unattended?

Code: Select all

MSI (s) (F0:20) [10:55:31:915]: Doing action: InstallInitialize
Action ended 10:55:31: RemoveExistingProducts. Return value 1.
MSI (s) (F0:20) [10:55:31:917]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (F0:20) [10:55:31:917]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (F0:20) [10:55:31:917]: BeginTransaction: Locking Server
MSI (s) (F0:20) [10:55:31:924]: Note: 1: 2265 2:  3: -2147287035 
MSI (s) (F0:20) [10:55:31:934]: Note: 1: 2265 2:  3: -2147287035 
MSI (s) (F0:20) [10:55:31:937]: Server Locked: Install is suspended for product {AC76BA86-1033-FF00-7760-BC15014EA700}
MSI (s) (F0:20) [10:55:31:937]: Checking in-progress install: install for different product.
MSI (s) (F0:20) [10:55:31:937]: Checking in-progress install: install for same configuration.
MSI (s) (F0:20) [10:55:31:937]: Note: 1: 1704 2: Adobe Acrobat (64-bit) 
Action start 10:55:31: InstallInitialize.
MSI (s) (F0:20) [10:55:31:938]: Product: Our Company Client -- Error 1704. An installation for Adobe Acrobat (64-bit) is currently suspended.  You must undo the changes made by that installation to continue.  Do you want to undo those changes?
MSI (s) (F0:20) [10:55:31:945]: Note: 1: 2265 2:  3: -2147287035 
MSI (s) (F0:20) [10:55:31:948]: Machine policy value 'DisableRollback' is 0
Error 1704. An installation for Adobe Acrobat (64-bit) is currently suspended.  You must undo the changes made by that installation to continue.  Do you want to undo those changes?
MSI (s) (F0:20) [10:55:31:953]: Note: 1: 2318 2:  
MSI (s) (F0:20) [10:55:31:973]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1535871053,LangId=0,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (F0:20) [10:55:31:973]: Executing op: DialogInfo(Type=0,Argument=0)
MSI (s) (F0:20) [10:55:31:974]: Executing op: DialogInfo(Type=1,Argument=Adobe Acrobat)
MSI (s) (F0:20) [10:55:31:974]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])

[Catalin]

Hello,

I think we should be able to enable the “Prevent running if pending system changes that require a reboot is detected” launch condition but we worry that will create more issues than it fixes. When apps are delivered via things like ConfigMgr/SCCM or Intune, multiple MSIs might be installed and we'd rather not fail our installer if one of them needs a reboot.

Not quite sure whether this is a good approach here, as that launch condition mostly is related to pending system reboots (for example from a Windows Update). In our case, the pending reboot is scheduled during the installation, not before, and therefore the launch condition (which is evaluated before the setup starts) will not take effect.

In the log, you see it asking us if we want to undo the other app's changes (Adobe). The default appears to be 'yes, is there a way to default that to 'no' when ran unattended?

Here, I'm afraid I don't know whether that is possible or not, because it's not in our control.

If Adobe has such an option, for example a command line parameter that does that, then yes, we can use Advanced Installer to automatically pass that parameter to the Adobe setup - but this is entirely up to the devs of the installation package of your prerequisite (i.e. if they added such a parameter).


Best regards,
Catalin