Rasmus Haslund

Virtualize everything!

  • LinkedIn
  • RSS
  • Twitter
  • YouTube
  • Home
  • Videos
  • Practice Exams
    • VMCE practice exam – Veeam Certified Engineer
  • EqualLogic
  • Veeam
  • VMware
  • About

Veeam troubleshooting: 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.

2012-09-25 by Rasmus Haslund 4 Comments

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).

Quick fix
#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

UPDATE 2012-12-18
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.

UPDATE 2013-07-26
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
  • failed to login to vcenter server by soap port 443
  • veeam restore login failure restore soap 443

Filed Under: Fix IT, Veeam Tagged With: error, Veeam, VMware, vSphere

Subscribe
Connect with
Login
I allow to create an account
When you login first time using a Social Login button, we collect your account public profile information shared by Social Login provider, based on your privacy settings. We also get your email address to automatically create an account for you in our website. Once your account is created, you'll be logged-in to this account.
DisagreeAgree
Notify of
I allow to create an account
When you login first time using a Social Login button, we collect your account public profile information shared by Social Login provider, based on your privacy settings. We also get your email address to automatically create an account for you in our website. Once your account is created, you'll be logged-in to this account.
DisagreeAgree
Please login to comment
4 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Robert
8 years ago

Had similar issue. It occurred after I changed my domain admin password. Found out the the VCenter server that I had listed under servers in VEEAM 6.0 had embedded authentication that I also had to change.

0
paul parkin
8 years ago

Hi Guys,

I just tried this with Veeam B&R 6.5, Windows 2012 server and vSphere 5.1 and I still get the same error as above, as I did when I tested on Windows 2008 server.

Workaround seems to work OK, just like in 2008 server.

0
Rasmus Haslund
8 years ago
Reply to  paul parkin

Thank you for the follow-up Paul.
I would recommend opening a support case with Veeam, so we can get this resolved.

Happy to hear that the workaround helped.

0
Hayrettin Duzgun
7 years ago

İts done thanks..

0

Sponsors

wpDiscuz