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
9,3967 gold badges46 silver badges64 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.1k15 gold badges55 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
98212 silver badges17 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
4403 silver badges10 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,4041 gold badge17 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
9,3967 gold badges46 silver badges64 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.1k15 gold badges55 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
98212 silver badges17 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
4403 silver badges10 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,4041 gold badge17 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
8,3095 gold badges40 silver badges57 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
10k15 gold badges55 silver badges69 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
95311 silver badges17 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
4403 silver badges10 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,4041 gold badge17 silver badges27 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
Обновлено 15.05.2016
Всем привет сегодня расскажу как решается ошибка Error 1920.Service MSMFramework (MSMFramework) failed to start. Verify that you have sufficient privileges to start system services при установке MegaRAID Storage Manager. напомню MegaRAID Storage Manager или как ее еще называют MSM, это утилита для мониторинга и работы с контроллерами LSI.
Описание ситуации
Есть сервер под Windows Server 2008 R2, на нем стоит RAID контроллер ServeRAID M5015 на базе LSI 9260-8i, при попытке поставить утилиту MegaRAID Storage Manager выскакивает ошибка, что не возможно запустить службу утилиты.
Error 1920.Service MSMFramework (MSMFramework) failed to start. Verify that you have sufficient privileges to start system services
Установка MSM
Как видите, что кроме отмены и повторной попытки ничего сделать не получается.
Решение проблемы
Поискав информацию на просторах интернета, было найдено несколько вариантов. В начале попробуйте во время того как у вас выскочит диалоговое окно с кнопкой Retry, откройте командную строку от имени администратора и попробуйте в ручную запустить службу MSMFramework. Если все ок, то установка MSM продолжиться, если нет то вы получите ошибку
запуск службы MSMFramework
Это уже небольшая победа так как мы выяснили, что запуск службы MSMFramework не возможен по причине, того что есть дополнительный сервис который не работает.
Так же более детальный лог установки утилиты LSI можно посмотреть в файле MSM_install, лежит он в той же папке где и дистрибутив установщика.
Вот небольшая выдержка из этого файла
Info 2835.The control ErrorIcon was not found on dialog SetupError.
Error 1920.Service MSMFramework (MSMFramework) failed to start. Verify that you have sufficient privileges to start system services.
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1288788 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1296368 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1300576 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1267836 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1265760 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1300736 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1287160 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1299780 could not be cancelled. Error: 1168
MSI (s) (90:D8) [12:12:26:187]: I/O on thread 1292168 could not be cancelled. Error: 1168
MSI (s) (90:00) [12:12:26:203]: Product: MegaRAID Storage Manager — Error 1920.Service MSMFramework (MSMFramework) failed to start. Verify that you have sufficient privileges to start system services.
лог ошибки
Зайдем в Администрирование-Службы
тут нам необходимо определить какие зависимые службы у MSMFramework. Выбираем службу MegaRAID Storage Manager, щелкаем правым кликом и переходим в Зависимости. Видим, что для работы необходима работающая служба Инструментарий управления Windows.
зависимые службы у MSMFramework
Запустив Инструментарий управления Windows ваша установка MSM продолжится в штатном режиме.
Вот так вот просто решается ошибка Error 1920.Service MSMFramework (MSMFramework) failed to start. Спасибо за внимание. Если у вас есть вопрос, то задавайте их в комментариях.
Материал сайта pyatilistnik.org
-
Bass
- OpenVpn Newbie
- Posts: 2
- Joined: Mon Mar 14, 2022 5:14 pm
Can’t install OpenVPN (Service OpenVPN Interactive Service failed to start)
Hello
I am trying to install OpenVPN (OpenVPN-2.5.5-I602-amd64.msi) on Windows 7 x64 and I get the error message:
«Service ‘OpenVPN Interactive Service’ (OpenVPNServiceInteractive) failed to start. Verify that you have sufficient privileger to start system services.»
I saw the same problem on this forum and the advice is to run the installer as an administrator.
However, the installer asks for the administrator password, so I think it works with administrator rights.
But I also tried to run the installer from administrator forcibly.
The .msi file doesn’t have the «Run as administrator» option, so I run cmd.exe as administrator, and then runs OpenVPN-2.5.5-I602-amd64 from there — and get the same error
Please help
-
openvpn_inc
- OpenVPN Inc.
- Posts: 1118
- Joined: Tue Feb 16, 2021 10:41 am
Re: Can’t install OpenVPN (Service OpenVPN Interactive Service failed to start)
Post
by openvpn_inc » Sat Mar 19, 2022 3:46 pm
Hi Bass (is that the fish or the musical term?)
This is basically a Windows question, not an openvpn one. But you seem to be misunderstanding the difference between running the installer and starting the service. Sure, you ran as Administrator when you did the install. You must also start the service as Administrator.
I know you can right-click the icon to get a context menu which will include a «Run as Administrator» option. I don’t know anything about starting services on Windows 7, except that it is the same idea: only Administrator can run services which require Administrator privileges.
regards, rob0
OpenVPN Inc.
Answers provided by OpenVPN Inc. staff members here are provided on a voluntary best-effort basis, and no rights can be claimed on the basis of answers posted in this public forum. If you wish to get official support from OpenVPN Inc. please use the official support ticket system: https://openvpn.net/support
-
Bass
- OpenVpn Newbie
- Posts: 2
- Joined: Mon Mar 14, 2022 5:14 pm
Re: Can’t install OpenVPN (Service OpenVPN Interactive Service failed to start)
Post
by Bass » Sat Mar 19, 2022 5:53 pm
Thanks for the answer, Rob0!
Musical 
I figured it out myself.
I’m logged in as an administrator and repeated the installation and saw error messages about unsigned drivers.
(when I’m logged in as regular user, and doing Run As — these messages were not shown)
The service didn’t start, because the drivers were not installed.
I install version 2.5.3 — with signed drivers, and it works fine
B.
- Remove From My Forums
-
General discussion
-
I am getting Error 1920. Service ABC (ABC) failed to start. Verify that you have sufficient privilege to start system services while installing a web application.
I know for sure that I have sufficient privilege to start the services. In fact, I was able to install a week ago, but decide to remove it. When I try to install again, I keep getting Error 1920, any idea in resolving this issue please? I am suspecting a registry issue or while uninstalling there could be remnant from the uninstalling? Please help
thanks
J
Jformn
- Edited by
Thursday, September 3, 2009 5:08 PM
- Changed type
jformn
Thursday, September 3, 2009 5:50 PM
- Edited by
Hi tronixmart, the problem is not a bad key. . .
First of all, if you are using Win 7 Home Premium (as I am), Home Basic, or Starter, you will not have a Local Users and Groups option. It is only for Win 7 Ultimate, Professional, or Enterprise.
Jennifer Zhan’s second suggestion regarding the changing of ‘This account’ to ‘Local system account’ under the «Log on» tab in the properties window of Office Software Protection Platform is better, but still not adequate. If you try this, as I
did, and then manually start Office Software Protection Platform before continuing the Office 2010 installation from the point of error, you will receive a new surprise. The Error 1920 message goes away, but then it is replaced with an oh-so-descriptive dialogue
box telling you that «Microsoft Office 2010 installation encountered an error.» Nice.
Changing ‘This account’ to ‘Local system account’ is useless, because after the error described above, the system somehow reverts the log on selection for Office Software Protection Platform back to ‘This account,’ with ‘Network service’ selected by default.
The better solution is to give the user account called ‘Network service’ full permissions for the appropriate folders and registry entries. Simply follow these instructions I found on another forum:
In Windows Explorer:
Right Click on the folder OfficeSoftwareProtection Platform
from C:Program FilesCommon FilesMicrosoft Shared and Microsoft from
C:Program data(hidden folder) Properties > Security > Edit > Add > Type Network Service > OK > Check the Full control box > Apply and OK.
In Registry Editor (regedit.exe):
Go to HKEY_CLASSES_ROOTAppID registry >Right Click on the folder > Permissions > Add > TypeNETWORK SERVICE > OK > Check Full Control > Apply > OK
This worked for me and many others with the same problem, and took mere minutes to do.
- Marked as answer by
Thursday, November 18, 2010 7:14 AM
June 10, 2020
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
How to Review the Service Log Files
Each of the Veeam services has its own respective service log file. Often when the service is failing to start for any reason other than permissions, the service will write information that can help with the resolution to its log file.
The service log files are written to C:ProgramDataVeeamBackup and have a filename pattern of Svc.<service>.log. You may find it convenient to navigate to that folder, then sort by date modified, then attempt to start the service manually. This will cause the appropriate service log to be easier to identify. Another tip is that after opening the log file, press Ctrl+END to go to the bottom, then begin reading the log from bottom to top, and look for lines containing > Error. Log reading is a skill, one that Veeam Support is trained and ready to assist you with.
- Veeam Backup Service
Svc.VeeamBackup.log - Veeam Data Mover Service
Svc.VeeamTransport.log - Veeam vPower NFS Service
Svc.VeeamNFS.log - Veeam Backup Enterprise Manager
Svc.VeeamBES.log