We have created a custom windows service. The deployment package is done in InstallShield and the installation prompts for the user name and password for the service Log On account.
We have had no issues at all installing on various Windows 7 (Professional) and Windows 8 machines, but we get the 1920 error when trying to deploy to a Windows 7 Ultimate machine. We have not yet confirmed whether the issue is to do with the OS or the specific machine that we are trying to install this on.
The installer is always run by right-clicking and «Run as Administrator», and the users (both, the user running the installer and the Logon User for which the credentials are supplied) are administrators on the machine. Usually the logged in user installing the service, and the Logon user running the service are the same.
Here are the things we have tried.
- Verified the Logon user is a member of Administrators.
- Verified the user account settings are exactly the same as another machine where it works.
- Verified from Control Panel — Administrative tools — Local Security Policy — Local Policies — Security Options = that these again match machine where it works.
- Ensured that all windows updates have been applied.
- Verified that the Windows Management Instrumentation Service is running. Restarted it.
- Rebooted the machine, then tried again.
- Added «generatePublisherEvidence» element in the service configuration file. (Service failed to start error 1920)
But none of the above work.
Hope that someone else has come across a similar issue and has a fix..
UPDATE:
I have also tried the following:
- Open SecPol.msc
- Navigate to Local Policies/User Rights Assigment
- Find «Log on as a service» policy and add the service account
riQQ
10.1k7 gold badges50 silver badges68 bronze badges
asked Nov 19, 2013 at 0:50
1
1920 is a generic error code that means the service didn’t start. My hunch is this:
http://blog.iswix.com/2008/09/different-year-same-problem.html
To confirm, with the installer on the abort, retry, ignore, cancel dialog up… go into services.msc and set the username and password manually. If you get a message saying the user was granted logon as service right, try hitting retry on the MSI dialog and see if it starts.
It could also be missing dependencies or exceptions being thrown in your code.
answered Nov 19, 2013 at 0:54
10
I also had the same issue. I fixed this by installing the .NET framework version 4.5.
hichris123
10.2k15 gold badges56 silver badges70 bronze badges
answered May 19, 2014 at 1:49
1
Make sure all services windows are closed before starting install/uninstall
answered May 22, 2015 at 14:19
MarkusMarkus
1,03814 silver badges19 bronze badges
3
In my case I had to delete the services in my installshield project and start from square one. My original service components were added manually and I couldn’t get them working, the only error I was getting was the same «Error 1920 service failed to start. Verify that you have sufficient privileges to start system services.» that you were getting. After deleting my components, I re-added them using the component wizard.
I actually had to create two new components. One was of type «Install Service».
The other component I had to add was of «Control Service» type.
I had to choose the service that I had setup when I added the Install Service component.
After that it worked, even though nothing looked differently from the components I had added manually. Installshield must do something behind the scenes when it wires up the service components with the component wizard.
All of this was with Install Shield 2016.
answered Jun 1, 2017 at 19:58
nickonicko
4703 silver badges11 bronze badges
1
Workaround: This is a problem we have observed too, in Windows Server 2012 R2. I haven’t found a reason or solution yet. Here is my work around.
During installation while error is shown, go to Services.msc. Find the service which throws the error, then re-enter the password in the service’s log-in information. Then, hit «retry» in setup. It works.
The error will not be shown for same user again. But will be shown for a different user.
answered Oct 21, 2016 at 9:15
1
Open Event Viewer go to window logs->Application and look at the errors prior to this error it will give you the actual error you looking to solve
answered Jan 16, 2018 at 14:54
Teezy7Teezy7
5155 silver badges9 bronze badges
1
In my case, the service failed to start because I didn’t set Platform='x64' in the wix file.
I saw these errors in Event Viewer:
Service cannot be started.
System.BadImageFormatException: Could not load file or assembly ‘SOME_LIBRARY_FILE, Version=5.0.0.0, Culture=neutral, PublicKeyToken=33345856ad364e35’ or one of its dependencies.
I tried checking the bitness of all service related files using CorFlags.exe. When I changed my installer to be 64 bit, everything started working fine.
answered May 23, 2014 at 18:12
Check service dependencies if they are disabled.
Set those dependencies to Automatic, Start them and it should work.
answered Apr 28, 2017 at 10:58
Ivan ChauIvan Chau
1,4031 gold badge18 silver badges28 bronze badges
1
I had this issue while testing software.
Drivers were not signed.
Tip for me was:
in cmd line: (administrator)
bcdedit /set TESTSIGNING ON
and reboot the machine (shutdown -r -t 5)
answered Mar 7, 2017 at 15:02
We have created a custom windows service. The deployment package is done in InstallShield and the installation prompts for the user name and password for the service Log On account.
We have had no issues at all installing on various Windows 7 (Professional) and Windows 8 machines, but we get the 1920 error when trying to deploy to a Windows 7 Ultimate machine. We have not yet confirmed whether the issue is to do with the OS or the specific machine that we are trying to install this on.
The installer is always run by right-clicking and «Run as Administrator», and the users (both, the user running the installer and the Logon User for which the credentials are supplied) are administrators on the machine. Usually the logged in user installing the service, and the Logon user running the service are the same.
Here are the things we have tried.
- Verified the Logon user is a member of Administrators.
- Verified the user account settings are exactly the same as another machine where it works.
- Verified from Control Panel — Administrative tools — Local Security Policy — Local Policies — Security Options = that these again match machine where it works.
- Ensured that all windows updates have been applied.
- Verified that the Windows Management Instrumentation Service is running. Restarted it.
- Rebooted the machine, then tried again.
- Added «generatePublisherEvidence» element in the service configuration file. (Service failed to start error 1920)
But none of the above work.
Hope that someone else has come across a similar issue and has a fix..
UPDATE:
I have also tried the following:
- Open SecPol.msc
- Navigate to Local Policies/User Rights Assigment
- Find «Log on as a service» policy and add the service account
riQQ
10.1k7 gold badges50 silver badges68 bronze badges
asked Nov 19, 2013 at 0:50
1
1920 is a generic error code that means the service didn’t start. My hunch is this:
http://blog.iswix.com/2008/09/different-year-same-problem.html
To confirm, with the installer on the abort, retry, ignore, cancel dialog up… go into services.msc and set the username and password manually. If you get a message saying the user was granted logon as service right, try hitting retry on the MSI dialog and see if it starts.
It could also be missing dependencies or exceptions being thrown in your code.
answered Nov 19, 2013 at 0:54
10
I also had the same issue. I fixed this by installing the .NET framework version 4.5.
hichris123
10.2k15 gold badges56 silver badges70 bronze badges
answered May 19, 2014 at 1:49
1
Make sure all services windows are closed before starting install/uninstall
answered May 22, 2015 at 14:19
MarkusMarkus
1,03814 silver badges19 bronze badges
3
In my case I had to delete the services in my installshield project and start from square one. My original service components were added manually and I couldn’t get them working, the only error I was getting was the same «Error 1920 service failed to start. Verify that you have sufficient privileges to start system services.» that you were getting. After deleting my components, I re-added them using the component wizard.
I actually had to create two new components. One was of type «Install Service».
The other component I had to add was of «Control Service» type.
I had to choose the service that I had setup when I added the Install Service component.
After that it worked, even though nothing looked differently from the components I had added manually. Installshield must do something behind the scenes when it wires up the service components with the component wizard.
All of this was with Install Shield 2016.
answered Jun 1, 2017 at 19:58
nickonicko
4703 silver badges11 bronze badges
1
Workaround: This is a problem we have observed too, in Windows Server 2012 R2. I haven’t found a reason or solution yet. Here is my work around.
During installation while error is shown, go to Services.msc. Find the service which throws the error, then re-enter the password in the service’s log-in information. Then, hit «retry» in setup. It works.
The error will not be shown for same user again. But will be shown for a different user.
answered Oct 21, 2016 at 9:15
1
Open Event Viewer go to window logs->Application and look at the errors prior to this error it will give you the actual error you looking to solve
answered Jan 16, 2018 at 14:54
Teezy7Teezy7
5155 silver badges9 bronze badges
1
In my case, the service failed to start because I didn’t set Platform='x64' in the wix file.
I saw these errors in Event Viewer:
Service cannot be started.
System.BadImageFormatException: Could not load file or assembly ‘SOME_LIBRARY_FILE, Version=5.0.0.0, Culture=neutral, PublicKeyToken=33345856ad364e35’ or one of its dependencies.
I tried checking the bitness of all service related files using CorFlags.exe. When I changed my installer to be 64 bit, everything started working fine.
answered May 23, 2014 at 18:12
Check service dependencies if they are disabled.
Set those dependencies to Automatic, Start them and it should work.
answered Apr 28, 2017 at 10:58
Ivan ChauIvan Chau
1,4031 gold badge18 silver badges28 bronze badges
1
I had this issue while testing software.
Drivers were not signed.
Tip for me was:
in cmd line: (administrator)
bcdedit /set TESTSIGNING ON
and reboot the machine (shutdown -r -t 5)
answered Mar 7, 2017 at 15:02
Last updated on June 24, 2020
The log on as a service user right allows accounts to start or run services on a Windows machine. By default, and due to security reasons, services can only be configured to run under the Local System, Local Service or Network Service accounts which have a built-in right to log on as a service. Any other user account that requires to run a service must be assigned this right.
When installing Parallels® Remote Application Server (RAS), if the user that is logged on does not have sufficient privileges to install system services, the following error may appear:
“Service ‘RAS RD Session Host Agent’ (RAS RD Session Host Agent) failed to start. Verify that you have sufficient privileges to install system services”.
Resolution
- Run gpedit.msc.
- Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies >User Rights Assignment.
- In the details pane, double-click Log on as a service.
- Click Add User or Group… and add the account to the list of accounts that have the Log on as a service right. Once you have selected the user, click OK.
- Click OK and close the policy editor.
Supported on
RAS RD Session Host Agent is supported on the following operating systems:
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2
- Windows Server 2008
Related How To’s
Service… failed to start. Verify that you have sufficient privileges to start system services
References
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/log-on-as-a-service
I tried to install Jenkins on Windows 7 home edition and got the following error.
Service ‘Jenkins’ (Jenkins) failed to start. Verify that you have sufficient privileges to start system services.
I have admin rights for my user account but still not able to install Jenkins.
Please help.
asked Feb 11, 2016 at 20:46
Try right clicking the setup file and pressing «Run as administrator» before launching. This should run the setup file with escalated privileges and resolve your issue.
answered Feb 12, 2016 at 0:09
AbraxasAbraxas
4,3066 gold badges30 silver badges47 bronze badges
Open cmd prompt -> net user administrator-> If account active is showing NO -> Then type these command to active — > net user administrator /active:yes
It worked perfectly in my case!
answered Nov 27, 2020 at 8:38
don’t close retry and cancel button at this stage,
instead go to services in windows and right click on jenkins service properties and click on logon then choose this account and and pick account in pc(whatever account you are choosing that account should have log on as service- local security option).
now click on retry option in jenkins installation
this will solve the problem
answered Apr 30, 2021 at 6:44
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
Issue
We have created a custom windows service. The deployment package is done in InstallShield and the installation prompts for the user name and password for the service Log On account.
We have had no issues at all installing on various Windows 7 (Professional) and Windows 8 machines, but we get the 1920 error when trying to deploy to a Windows 7 Ultimate machine. We have not yet confirmed whether the issue is to do with the OS or the specific machine that we are trying to install this on.
The installer is always run by right-clicking and “Run as Administrator”, and the users (both, the user running the installer and the Logon User for which the credentials are supplied) are administrators on the machine. Usually the logged in user installing the service, and the Logon user running the service are the same.
Here are the things we have tried.
- Verified the Logon user is a member of Administrators.
- Verified the user account settings are exactly the same as another machine where it works.
- Verified from Control Panel – Administrative tools – Local Security Policy – Local Policies – Security Options = that these again match machine where it works.
- Ensured that all windows updates have been applied.
- Verified that the Windows Management Instrumentation Service is running. Restarted it.
- Rebooted the machine, then tried again.
- Added “generatePublisherEvidence” element in the service configuration file. (Service failed to start error 1920)
But none of the above work.
Hope that someone else has come across a similar issue and has a fix..
UPDATE:
I have also tried the following:
- Open SecPol.msc
- Navigate to Local Policies/User Rights Assigment
- Find “Log on as a service” policy and add the service account
Solution
1920 is a generic error code that means the service didn’t start. My hunch is this:
http://blog.iswix.com/2008/09/different-year-same-problem.html
To confirm, with the installer on the abort, retry, ignore, cancel dialog up… go into services.msc and set the username and password manually. If you get a message saying the user was granted logon as service right, try hitting retry on the MSI dialog and see if it starts.
It could also be missing dependencies or exceptions being thrown in your code.
Answered By – Christopher Painter
This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0