Comprehensive data protection for all workloads
Post Reply
singy2002
Service Provider
Posts: 63
Liked: 1 time
Joined: Mar 22, 2010 8:43 am
Full Name: Andrew Singleton
Contact:

Authentication to VCenter Server

Post by singy2002 »

Hi,

We encountered an issue with the replication task on Monday, one of the domain controllers was rebooting as part of a scheduled restart.

The replica job was then unable to authenticate against the VC. The error generated is below.

Checking "ESXSERVER.domain" host license level Failed to login to "VC" by SOAP, port 443, user "DOMAIN\USername", proxy srv: port:0 Exception has been thrown by the target of an invocation. Cannot complete login due to an incorrect user name or password.

We have a secondary domain controller which was available for authentication, should veeam not have authenticated against the other DC?

DC1 - reboots 11pm

Replica job 1 - starts 23:00:19
Replica job 2 - starts 23:00:19

The next entry in the job log is :

Status Success Start time 17/05/2010 23:10:46 Details
Total VMs 0 End time 17/05/2010 23:11:06 There are no objects to backup
Processed VMs 0 Duration 0:00:20
Successful VMs 0 Total size 0.00 KB
Failed VMs 0 Processed size 0.00 KB
VMs in progress 0 Processing rate 0 KB/s

The primary DC was back online at ~23:03

The next job ran successfully at 1AM (2 hour schedule)

Gostev
SVP, Product Management
Posts: 26701
Liked: 4276 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Authentication to VCenter Server

Post by Gostev »

Hello, according to the error, the issue here is with vCenter Server not being able to validate credentials Veeam Backup has provided against Active Directory. Veeam Backup does not connect to AD here, as in this case Veeam Backup is a client application, and vCenter is a server application that has to process the logon by validating the provided credentials against AD. This process is what failed, for some reason vCenter failed to connect to the remaining DC. Or, there are replication issues between DCs, and the second DC contains old account password. vCenter server logs should contain exact reason.

Generally, if AD has no issues, this issue should not happen assuming vCenter implements Microsoft recommendations on working with AD, and uses serverless bind instead of specifying exact DC to connect to, and "sticking" to it.

singy2002
Service Provider
Posts: 63
Liked: 1 time
Joined: Mar 22, 2010 8:43 am
Full Name: Andrew Singleton
Contact:

Re: Authentication to VCenter Server

Post by singy2002 »

ok many thanks

SystemFuchs
Novice
Posts: 7
Liked: never
Joined: Apr 26, 2010 7:36 pm
Full Name: Stephan Fuchs
Contact:

Re: Authentication to VCenter Server

Post by SystemFuchs »

Hi singy2002,

where you able to resolve this issue? I'm recieving this error too?!

Regards

Stephan

Post Reply

Who is online

Users browsing this forum: Majestic-12 [Bot] and 37 guests