Try setting the network profile to if it defaulted to Public, which can block necessary traffic.
Since port 9392 is hard-coded for the Deploy Service, a conflict is the leading cause of startup failure. failed to start service veeamdeploysvc
| Scenario | Likely Fix | |----------|-------------| | After Windows Update | Reboot, then repair install | | On Hyper-V Server (free) | Install full Windows feature Hyper-V Management Tools | | After moving Veeam DB to another SQL instance | Re-run Veeam configuration wizard | | Cloned VM with same SID | Sysprep or reinstall Veeam components | | Insufficient disk space on %SystemDrive% | Free >500 MB for service temp files | Try setting the network profile to if it
| Port | Purpose | |------|---------| | 135 | RPC endpoint mapper | | 445 | SMB (file copy) | | 6160 | VeeamDeploySvc default | | 6162-6163 | Secondary deployment channels | He checked the Veeam Backup & Replication logs,
Alex was perplexed by the error message and didn't know where to start troubleshooting. He checked the Veeam Backup & Replication logs, but they didn't provide any clear indication of what was causing the issue. He then decided to investigate the Windows Event Viewer logs on the Veeam Backup & Replication server. After sifting through the logs, he found a series of errors related to the veeamdeploysvc service, but they were not very informative.
Is there a specific (like 0x00000002) in the logs?