- Veeam Support Knowledge Base
- Veeam Service Fails to Start with Error 1920
Veeam Service Fails to Start with Error 1920
| KB ID: | 1059 |
| Product: | Veeam Backup & Replication |
| Published: | 2011-07-19 |
| Last Modified: | 2022-04-27 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
Error 1920. Service <display_name> (<service_name>) failed to start. Verify that you have sufficient privileges to start system services.Solution
Common Causes
- The service is set to run as an account other than Local System, and the account credentials are wrong, or the account does not have logon as a service permissions.
- The port that the service is attempting to lock is already in use.
Related: KB2065 - The service relies upon a SQL Configuration database, which is inaccessible, or the service is not configured to connect to the correct database location.
Use the DBConfig Utility to identify which SQL Instance the software is attempting to connect to and verify that the SQL Database is accessible. - The vPower NFS Service may fail to start if the path for the 'RootFolder' value in the registry points to a drive that no longer exists. See KB1094
- Antivirus may be preventing the service from starting. See KB1999
- If the error occurs with Veeam Agent for Microsoft Windows on a machine running Windows 8.1 or Server 2012, there may be missing updates. See KB4142
- There is a restart pending for Windows updates preventing the service from being installed.
- There is corruption within the Windows OS.
Collect Logs and Open a Veeam Support Case
Veeam Support Engineers can review the service logs to help identify why the service won't start.
- Collect Veeam Logs
- If the Veeam Backup & Replication Console is accessible, use the built-in log collection tool to gather logs from the server where the service is failing to start.
- If the Veeam Backup & Replication Console is inaccessible, manually collect the service logs from C:\ProgramData\Veeam\Backup on the server where the service is failing to start. (Either collect all files from that folder or all files that begin with 'svc'.)
- In addition to Veeam logs, please also collect Windows Event logs.
- Once you have collected the logs, create a support case and attach them.
More information
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:\ProgramData\Veeam\Backup 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
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.