Good day everyone,
I upgraded veeam to version 9.5.0.1922 and adding the vcenter vcenter version 6.5. it errors with following message: Failed to login "vcenterserver" by SOAP port 443 user ""domainadmin", proxy srv: port:0
Any ideas possible causes?
Thanks in advance.
-
- Expert
- Posts: 187
- Liked: 12 times
- Joined: Sep 01, 2012 2:53 pm
- Full Name: Josue Maldonado
- Contact:
-
- Veteran
- Posts: 298
- Liked: 85 times
- Joined: Feb 16, 2017 8:05 pm
- Contact:
Re: Unable to add vcenter 6.5 case #03123165
It might be a credential issue; have a look at this post: https://forums.veeam.com/monitoring-f5/ ... 15520.html - the issue stated, and error message in particular, seems similar to your issue.
-
- Expert
- Posts: 187
- Liked: 12 times
- Joined: Sep 01, 2012 2:53 pm
- Full Name: Josue Maldonado
- Contact:
Re: Unable to add vcenter 6.5 case #03123165
thank for reply nitramd, vcenter services were installed with all defaults and runs under local system account, veeam services installed with all defaults and running under local system account.
Do you think I should change them both to run under domain administrator account?
Do you think I should change them both to run under domain administrator account?
-
- Veteran
- Posts: 298
- Liked: 85 times
- Joined: Feb 16, 2017 8:05 pm
- Contact:
Re: Unable to add vcenter 6.5 case #03123165
Changing the credentials to domain admin might be worth considering and may help, but then you run into the discussion of protecting your backups if your network is breached; you can view this lengthy ransomware post to get up to speed if you've not already: https://forums.veeam.com/veeam-backup-r ... 41500.html
If you can, I would suggest waiting for support to have a look at your case and see what they find or say.
If you can, I would suggest waiting for support to have a look at your case and see what they find or say.
-
- Expert
- Posts: 187
- Liked: 12 times
- Joined: Sep 01, 2012 2:53 pm
- Full Name: Josue Maldonado
- Contact:
Re: Unable to add vcenter 6.5 case #03123165
support helped us very fast, as suggested I just changed the user credentials to administrator@vSphere.local and worked just fine.
Who is online
Users browsing this forum: No registered users and 80 guests