A 'Login failure' is returned while attempting to configure a CloudLink task

book

Article ID: 100042945

calendar_today

Updated On:

Description

Error Message

When attempting to list the AD objects the following error occurs:

Logon failure: unknown user name or bad password

Image

In the Trace.log file (C:\Program Files\ArchiveTools\CloudLink\Logs\\Trace.log) the following error is found:

Failed to bind with RootDSE object of domain controller 'abc.com' Detail:
Logon failure: unknown user name or bad password.

Cause

The CL service account fails to authenticate to the domain controller preventing the AD information from being accessed properly. 

Resolution

Re-register the domain controller in CL:

Login to the CL server as the CL service account

Go to Configuration > Configuration Tasklist > Directory Synchronization Configuration > Register Domain Controller (on the left side of screen)

Image

  1. Select the registered domain and Remove it 
  2. Select Yes to delete all tasks of the domain controller
  3. Select the Domain Controller from the drop down list and Add it back again
  4. Put in the CL Service Account credentials
  5. Click Next on remaining configuration steps until the last steps is reached and select Finish

To test that it is working, create a new task and select Use a filter below to limit which user(s), group(s) and OU(s) will be synchronized to see if the AD objects can be listed properly. 

If removing the DC from CL doesn't resolve the issue the CloudLink.sdf file is corrupt or has data that can't get updated properly without assistance from Veritas Support.  Please create a case with Support to get further assistance and refer to this article.

Issue/Introduction

When attempting to configure a CloudLink (CL) task it fails with a login failure although the following has been checked:
  • CL service account has access to Active Directory (AD), Exchange, etc.
  • Cloud Archive credentials are successful when logging into the Manage portal.
  • ArchiveTools CL Server service is set to Log On As the CL service account.
  • CL application has been Run As Administrator.