Today one of our regular customers called with a wierd error. After upgrading their VMware ESXi hosts and vCenter to 5.1 (unsupported) they could suddenly no longer backup VMs one of their two hosts using Veeam.
The log would show:
Failed to login to “vcenter.domain.local” by SOAP, port 443, user “”, proxy srv: port:0
Cannot complete login due to an incorrect user name or password.
I am sure this is something that has been fixed in Veeam B&R 6.5 (soon to be released).
#1 Remove the vCenter from Veeam (unfortunately this means deleting all jobs currently using it or as a minimum remove the VMs from the job).
#2 Add each host as a standalone host with correct credentials
#3 Re-add vCenter
#4 Add the standalone hosts in the backup job
What seems to happen sometimes are that the ESXi host(s) upgraded from fx 4.1 to 5.1 will stay in the SQL database. You can manually go in and remove these, however make sure you make a database backup first and if you feel unsure then do not hesitate to call Veeam and ask for their help to resolve this.
Veeam has released patch 3 for Veeam Backup & Replication 6.5 which now solves this issue. Looking at their KB article 1751 we now see “Upgrading vCenter or ESX(i) hosts may result in duplicate hosts appearing under Managed Servers, causing jobs to fail with object not found errors“. If you have not already installed patch 3 I suggest you do that now.
Incoming search terms:
- failed to login to by soap port 443
- failed to login by soap port 443
- veeam failed to login to by soap
- veeam failed to login by soap port 443
- can not log onto vcsa 443 do to incorrect password
- veeam restore login failure restore soap 443