Failed to upgrade host components. Error 1920.Service Veeam WAN Accelerator Service failed to start.
Challenge
The Veeam WAN Accelerator component upgrade fails with the following error:
Failed to upgrade host components. Error: ''Error 1920.Service Veeam WAN Accelerator Service (VeeamWANSvc) failed to start. Verify that you have sufficient privileges to start system services.'
The Components Update wizard appears during the first launch of Veeam Backup & Replication Console after an upgrade.
Cause
The Veeam WAN Accelerator component upgrade failed to complete because the associated service could not start.
On the component server, in the C:\ProgramData\Veeam\Backup\Svc.VeeamWANSvc.log file, the following details indicate the issue related to a drive that is no longer present.
srv | RootFolder = D:\VeeamWAN srv | SendFilesPath = D:\VeeamWAN\Send srv | RecvFilesPath = D:\VeeamWAN\Recv srv | ERR |Fatal error srv | >> |boost::filesystem::create_directories: The system cannot find the path specified: "D:\" srv | >> |Unable to apply settings. See log for details. srv | >> |An exception was thrown from thread [ ]. srv | Stopping service...
The RootFolder is configured in the value WanRootCachePath within the key [ HKLM\SOFTWARE\Veeam\Veeam WAN Accelerator ].
Solution
To resolve the issue of the Veeam WAN Accelerator Service service not being able to start because the path specified in WanRootCachePath is invalid, do the following:
- Connect to the component server that was being upgraded.
- Delete the WanRootCachePath registry value.
Open an Administrative PowerShell console and execute the following command:
- Return to the Veeam Backup & Replication Console, and reattempt the Component Update.
Note: If the managed server where the Veeam WAN Accelerator component was upgraded is still assigned the WAN Accelerator role, edit its properties and update the WAN Cache path.
More Information
- When a role (e.g., WAN Accelerator, Proxy, vPower NFS Service, Mount Server) is assigned to a managed server, a related component package that enables that server to fulfill that role is installed on it.
- As each component package is installed on a managed server, entries are recorded in the 'hostcomponents' table of the Configuration Database to track where packages are installed.
- If a role is unassigned from a managed server, those components remain installed on the managed server in case that role is reassigned in the future.
- The component tracking entries for each managed server remain in the configuration database until that managed server is removed from Veeam Backup & Replication.
Scenario Example
A backup administrator, eager to test the WAN Accelerator feature without setting up a dedicated machine, assigns the role to an existing managed server. Following best practices, they equip the server with an SSD to use as the WAN Accelerator cache (D:). After successful testing, the administrator builds a new dedicated WAN Accelerator machine and adds it to Veeam Backup & Replication. They remove the WAN Accelerator role from the original server. Subsequently, the SSD is removed from the old server and repurposed. When the administrator later installs an upgrade for Veeam Backup & Replication, the first launch of the Veeam Backup & Replication Console triggers a prompt to update all components on remote managed servers. Unfortunately, the update for the old managed server fails because the WAN Accelerator installer cannot start the WAN Accelerator service – it attempts to access the cache path on the now-absent SSD, causing the service to fail to start.
The solution documented in this article resolves the issue preventing the WAN Accelerator service from starting, thereby allowing the Component Update process to be completed successfully.
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.
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.
Oops! Something went wrong.
Please, try again later.