Veeam Service Fails to Start with Error 1920

This error may occur for numerous reasons, and it will require a review of the service logs to pinpoint the cause.

Common causes are:

• 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.
• The service relies upon a SQL Configuration database, which is inaccessible, or the service is not configured to connect to the correct database location.
• 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 is occurring 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 that is preventing the service from being installed.
• There is corruption within the Windows OS.

1. Collect Veeam Logs
   1. 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.
   2. 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'.)
2. In addition to Veeam logs, please also collect Windows Event logs.
3. Once you have collected the logs, create a support case and attach them.