Error 1920 when using silent /q

Hi to all - new to the forum :)

Wonder if anyone could help with an issue im having with an MSI package when trying to deploy using the /qn option.

The MSI in question is being called with : msiexec /i "name of msi.msi" <other install options>

This works fines on a clean build of Windows XP Pro SP3 no problems which confirms options are all okay.

The issue is when deploying on machines within a large organisation where their is a few hundred pcs all on a domain. (this is where i suspect their is a security permission causing the issue possibly locking down something on the local machines or users)

When the same MSI is used on the machines in question, the verbose log file that I have enabled is stating :

Windows Installer Error 1920
Service '[2]' ([3]) failed to start. Verify that you have sufficient privileges to start system services.

It appears to do this when the StartServices action is called from within the Install Sequence. Looking at the MSI with ORCA it would appear the MSI is configured to rollback the install should the service fail to start. The MSI is configure to use the local SYSTEM account to start the service.

The MSI rolls back the install and nothing is installed. You can keep trying to reinstall using the silent install and it fails with the same message each time.

Where the funny part comes in, which im wondering if anyone has seen before, if you just double click the MSI as if you were going to complete a manual installation (not silent), the first dialog box appears :

  • windows installer - preparing to install

  • Installshield wizard - welcome to the installshield wizard screen.

If on this screen you press cancel, which then says are you sure you wish to cancel (yes or no) select yes, then it says installation wizard completed (obviously whole install cancelled) then click Finish.

If you now try to run the silent install, it works perfect. It would appear by doing the above, something must get written on the machine to allow the silent installation to start the service.

As we need to roll this out using SMS to a few hundred machines the above methis isnt really an option so was hoping someone would have some ideas?

Thanks in advance

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 12 years ago
Red Belt
I've never encountered the scenario you outline.

Use something like InstallWatch (or ProcMon, if you prefer to do it "live") to see what exactly is being changed by the initialisation of the IS wizard.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
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