OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 2760 days ago.
When attempting to add, edit, or rescan a Windows or Hyper-V server, or rescan a Protection Group that contains a Windows machine, the following error occurs: The system cannot find the file specified. Failed to start service 'VeeamDeploySvc'. Host: '<name>'. --tr:Error code: 0x00000002 Failed to start deployment service on the target host --tr:Failed to install service [VeeamDeploySvc] was not installed on the host [<name>].
Note: VeeamDeploySvc, Veeam Deployment Service, and Veeam Installer Service are all names for the same service. When Veeam Backup & Replication attempts to interact with a Windows machine, it will first attempt to contact the Veeam Deployment Service on its default port of 6160. If that fails, it will then connect to the Windows machine via RPC and check if the VeeamDeploySvc is present, and if present, attempt to start the service. If the service is not present, Veeam Backup & Replication will install the Veeam Deployment Service and initiate a connection to that service over port 6160. The errors discussed in this article occur because the VeeamDeploySvc, also known as Veeam Installer Service, is detected as being present but cannot be started due to an OS-level issue.
Verify Issue The following steps are to be performed on the remote machine that Veeam Backup & Replication is failing to connect to. Open Services.msc and verify that the Veeam Installer Service (VeeamDeploySvc) is present and in a stopped state.
As noted in the Cause section, when Veeam Backup & Replication first attempts to contact a Windows server, it will do so by attempting to reach the Veeam Installer Service on port 6160. If that port cannot be reached, or the service is not started on the remote machine, some tasks may fail with a different error: RPC function call failed. Function name: [GetSvcVersion]. Target machine: [:6160].
