If you receive the error “Failed to login to “x.x.x.x” by SOAP, port 443, user “”, proxy srv: port:0
Cannot complete login due to an incorrect user name or password” during a backup proceedure within veeam backup and replication its normally due to duplicate enteries within Veeams SQL database. This is normally caused by upgrading the versions of Vcenter/ESXi which forces Veeam to enter a duplicate entry to its SQL database.
Ensure that the backup job has the correct domain administrative username and password set within the task to rule out that the entry has not been changed accidentally by someone.
To correct the SQL database issues though you will need to open the SQL Management Studio and then the Veeam database and perform the following:
1: BACKUP BACKUP BACKUP, BEFORE YOU DO ANYTHING ELSE BACKUP THE DATABASE BY RIGHT CLICKING THE DATABASE CHOOSE TASKS AND THEN BACKUP, OR USE YOUR COMPANY STANDARD BACKUP METHOD FOR SQL DATABASES.
2: Expand the tables node of the Veeam database and select the dbo.Hosts entry.
3: right click the entry and select “Edit top 200 rows” which will display 200 rows within this table
4: Look through the enteries in the table and select the duplicate enteries with the old “Info” VMware version.
5: Right click each duplicate entry and delete it.
6: Exit the SQL Management Studio and restart the backup which should now work as expected.
If this does not work and you do not mind recreating the backup jobs you can open the Veeam enterprise console and remove all host/VC connections and backup jobs first and then perform the following:
1: AS PER POINT 1 ABOVE BACKUP THE DATABASE!!!!!!!
2: As point 2 above
3: As point 2 above
4: Delete all rows associated with the virtualcenter/hosts so the table is devoid of any information regarding your current virtualcenter/hosts.
5: Exit the SQL Management Studio and open the Veeam Enterprise console and recreate the Virtualcenter/Host connections and backup jobs then run the backups again which should now backup as expected.
Author: Dale Scriven
Subscribe to vhorizon
DisclaimerThis blog and any other post made by me on the internet is representative of my views only, they are not the views of my past/current/future employers.