One ESX is failing login Veeam B&R

[lluisclemente]

I've just configured my new vcenter and I'm experiencing problems on one ESX,
7/13/2012 1:13:30 PM :: Failed to login to "IP.IP.IP.IP" by SOAP, port 443, user "", proxy srv: port:0
Cannot complete login due to an incorrect user name or password.
If I move VM to the other ESX on the cluter It works, I just reinstaled ESX and VCenter, it used to work.
Any ideas.
I can browse https://IP both servers and Vcenter, so it shouldn't be conectivity problems.
Thanks in advance.
Regards

[Vitaliy S.]

Does the IP address mentioned in the error message belong to vCenter Serve or ESX server? Also could you please tell me if you have any credentials specified for this ESX server or you're using vCenter Server connection to backup VMs from this ESX server?

[lluisclemente]

Same Vcenter server , 2 ESX, credentials used ar vcenter ones, I have a local admin user that conects to vcenter, vcenter has full visibility.
I'm thinking of installing veeam on the vcenter, but not sure it would make it work.
I've tried to specify local esx credentials in veeam but It didn't solve it.
In "Files" I can't see datastores , so it could be credentials problem.
Any ideas/suggestions ?

[Vitaliy S.]

If you have two ESX(i) servers managed by the same vCenter Server and you're able to see and use both hosts via vSphere Client, then basically adding this vCenter Server to the backup console is all you need to start working with Veeam B&R.

I would suggest to contact our support team and let them guide you through the initial deployment process. Thanks!

[Cokovic]

We had similar issues when ugrading existing hosts or moving a complete cluster into a new vCenter. Reason was always a duplicate entry in the Veeam databse under dbo.Hosts.

If you are not familiar with SQL you should contact support to assist you with this. Otherwise you could take a look into this table and see if your ESXi servers are listed twice.

[lluisclemente]

I had to reinstall veeam B&R in other machine with new database, now it works, it seems DB was corrupted or somethin like that.
Thanks for all.

[mmauchley]

Looks like I having a similar issue. I see several duplicates in the dbo.hosts file...how do I know what duplicate is ok to remove?

Thanks,

Matt

[Cokovic]

There is an info column where you can see your ESX version.

[jeremyh8]

I had this occure when we upgraded from esx4.0 to esx5i. different method of conencting to the host. we blew away the database and started over. i guess it was a hand grenade approach but it worked.

[Vladimirf]

Hi everybody,
Yesterday i've upgraded our Veeam B&R 6.1p1 to 6.5 and after it all backups failed with same message:

Failed to login to "********" by SOAP, port 443, user "", proxy srv: port:0 Cannot complete login due to an incorrect user name or password.

i found that there was a duplicate entry for that specific server in dbo.hosts table.

Thanks

[ortoscale]

I've got same error after upgrade to 6.5 from 6.1 (which was previously 6.0 and 5.0).
editing dbo.hosts didn't help. I've also tried deleting jobs and recreating but also didn't help.

Then I've decided to do a fresh install and guess what. I've pick up new DB and still got same error. Insane, lost here.

[ZachW]

If you are still having this issue then please go about creating a ticket with Support and we will get you squared away.

[Vitaliy S.]

Can you try to connect to your hosts/vCenter Server via vSphere Client from the same machine? If it does work, then please contact our support team, as debug logs review is required to investigate this behavior further.

[ortoscale]

If you are still having this issue then please go about creating a ticket with Support and we will get you squared away.

Case # 00172140

i've done that.

[ortoscale]

support took a look. We find out that it's actually a VMware issue (I've also upgraded VMWare to 5.1). I've both Vcenter and Veeam on same server. I could still login to Vcenter with client with "use Windows session credentials", but failing when I've type in username and password by myself. Figure that out !! thanks Veeam for now

[tsightler]

With 5.1, because of the changes for SSO requirements, it's quite common that using the "<Domain>\<username>" format is now required when previously it would work with just the "<username>", leaving off the domain. When using "use Windows session credentials" the domain is passed automatically. I've seen this in lot's of environments at this point.

[ortoscale]

this one is a real pain. some info here: http://communities.vmware.com/thread/418759

[cgrebing]

We had the same error after moving the vCenter Database to a new Server at a customer.
The customer configured all Jobs to use the new vCenter, but at some VMs running on 2 Hosts out of 6 this error came up.
When I looking at the database these 2 servers had duplicate entries at the dbo.hosts table.
I deleted the second entry of each host and the Jobs went fine again.