Skip to main content

I am doing a fresh install of Veeam Backup & Replication 12.3 on Server 2019. The process gets to step 6 and I get a popup stating: “failed to start Veeam backupcdpsvc service”. I checked the error logs and one that I noticed was “a call to sspi failed see inner exception”. Has anyone seen these issues before. I have erased everything and tried to reinstall. I'm using the local account not a Domain account if that helps. 

What server OS are you installing VBR on ​@kghii ? Is this a ‘clean” server with nothing else on it? Only thing I can think of is you may have a port conflict with another service or application. Check the port requirements in the Guide:

https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120#cdp-components

..then run netstat to see if the Veea CDP service port is in conflict with something on the server. Also, try disabling Windows Firewall temporarily during install. Those are some things you can initially try if you haven't already. You can also look at install logs in %ProgramData%\Veeam\Setup\Temp to see if anything further shows in there more in detail on the error.

Best.


I am doing a fresh install of Veeam Backup & Replication 12.3 on Server 2019. The process gets to step 6 and I get a popup stating: “failed to start Veeam backupcdpsvc service”. I checked the error logs and one that I noticed was “a call to sspi failed see inner exception”. Has anyone seen these issues before. I have erased everything and tried to reinstall. I'm using the local account not a Domain account if that helps. 

hi ​@kghii 

I remember “sspi error” is due to TLS version conflict. You need to have TLS v1.3 enabled but it’s not supported in Windows Server 2019.  

As per your error looking for the official forum i’ve found this solution 

https://forums.veeam.com/post521535.html#p521535

 

Please try adding VBR FQDN instead IP Address. 

Let us know if you need more suggestions. 


Are you using Postgres as the database?  What user are you installing as they may not have permission.  Check this KB - https://www.veeam.com/kb4542