Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

ADSynchroniser.exe 500 failed logins

Created: 09 Mar 2013 • Updated: 13 Mar 2013 | 4 comments
Scott _Hastings's picture
This issue has been solved. See solution.

I'm getting fussed at from my Security Group. The ADsynchronizer is putting over 500 events in the Security Event log: Any ideas on resolving this? Failed Login event for prod\evadmin on (Domain Controller) %NICWIN-4-Security_4625_Microsoft-Windows-Security-Auditing: Security,rn=526940507 cid=0x00003100 eid=0x00001211,Wed Mar 06 06:01:03 2013,4625,Microsoft-Windows-Security-Auditing,None,Failure Audit,QTC-(Domain Controller) ,Logon,,An account failed to log on. Subject: Security ID: /NULL SID Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 Account For Which Logon Failed: Security ID: /NULL SID Account Name: prod\evadmin Account Domain: Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc0000064 Process Information: Caller Process ID: 0x0 Caller Process Name: - Network Information: Workstation Name: CA Server Source Network Address: XX.XX.XX.XX Source Port: 25967 Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. The reason for failure is that domain\evadmin with Domain Name: does not exists.

Operating Systems:

Comments 4 CommentsJump to latest comment

Kenneth Adams's picture

From the error description, it seems as though either the DA server has lost its membership in the domain or the Vault Service Account (VSA) credentials have become changed or stale.  I recommend first refreshing the VSA credentials for the Enterprise Vault Accelerator Manager Service (EVAMS), then restarting EVAMS.

If the credentials refresh does not work, ensure you know the local Administrator account password for the DA server, then stop EVAMS and boot the DA server.  When the DA server comes back up, try logging onto it as the VSA.  If that fails, then  you will likely have to remove the server from the domain using its local Administrator account, boot the server, then add it back to the domain and boot the server again.

Ken

Ken Adams

Backline Support for CA, DA, ACE, UCE, PSTD, ARMS, EVDC
US Support Region

SOLUTION
Scott _Hastings's picture

Thanks Ken.. I reset the EVAMS Service password. Let's see what happens.

I'll let you know.

Scott _Hastings's picture

Thanks Kenneth. as it turns out, our security group was auditing multiple, consecutive logins to a DC and  adsyncronizer does this routinely when it is syncing custodians.

They added an expection.

Kenneth Adams's picture

Thank you for the update, Scott.  That's good information to know.

Ken Adams

Backline Support for CA, DA, ACE, UCE, PSTD, ARMS, EVDC
US Support Region