https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxODI4IiwiaGFzaCI6IjM2ZWM3YThjLWIwYzUtNDgwNi05N2FjLWU0OWU3MTU3OTBjNCJ9
1-800-691-1991 | 9am - 8pm ET
EN

WAN Accelerator Fails to Install

Challenge

Error message “Installing package VeeamWANSvc_x64.msi Error: Error 1920. Service Veeam WAN Accelerator Service (VeeamWANSvc) failed to start. Verify that you have sufficient privileges to start system services.” appears when trying to add a WAN Accelerator in the Backup Infrastructure. Trying to install the service manually on the proxy also fails.

User-added image

Cause

The service installer is pointing to an invalid path in the Registry on the server. This occurs most often when the role is removed from the server, then the original drive used for the WAN Accelerator cache was removed.

Solution

On the WAN Accelerator server having an issue reinstalling, open regedit and browse down to the following location:

HKLM>Software>Veeam>Veeam WAN Accelerator
 
Find the following Registry Strings and modify to point to a valid directory path:

HashRepositoryBasePath 
HashRepositoryGlobalDedupBasePath 
WanRootCachePath 

KB ID:
1828
Product:
Veeam Backup & Replication
Version:
7.x
Published:
2013-11-07
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later