• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1710
  • Last Modified:

Event ID 12292

Hi all,

Please help. I got lot of error with the below Event Log:

Event Type:      Error
Event Source:      SAM
Event Category:      None
Event ID:      12292
Date:            8/24/2004
Time:            6:23:14 PM
User:            ASIAPAC\AP-2K820$
Computer:      AP-2K220
There are two or more objects that have the same account name attribute in the SAM database. The Distinguished Name of the account is CN=File-Server,OU=Domain Controllers,DC=domain,DC=com,DC=my. Please  contact your system administrator to have all duplicate accounts deleted,  but ensure that the original account remains. For computer accounts, the  most recent account should be retained. In all the other cases, the older  account should be kept.

Thanks for your input.
  • 2
1 Solution
Perform a search in AD Users and computers for the account in question. All duplicates including the original will show up. Delete all but the original to get rid of the error.
From MS TechNet website:
"Fixing All Account Collisions by Examining the Event Logs for 12292 Events:
Object collisions are normal occurrences in a multi-mastered database environment where the rate of change is high and where the number of database replicas is also high.
The most common type of object collision in an environment occurs with computer account objects. A typical scenario is that a user joins a computer to a domain while talking to one domain controller, then immediately tries to use that computer object when talking to a different domain controller located somewhere else. Before replication resolves the discrepancy, the user then retries the join operation while talking to a different domain controller. The result of this sequence of events is a collision between two identically-named objects.
Active Directory recognizes these collisions and generates a 12292 event in the system event log. Active Directory will continue to generate these events until the situation is manually resolved by an administrator. Administrators should check for the 12292 events on a weekly basis, and resolve them by renaming or deleting the offending objects, which are described in the event text."
Disabled the service (rebooted) and now get Event ID 12289 (Volume Shadow Copy Service error: Unexpected error CoCreateInstance(CLSID_VSSCoordinator).  hr = 0x80070422. ) and event ID 39 (Volume Shadow Copy Service error:  The Volume Shadow Copy service (VSS) is disabled.  Please  enable the service and try again. )
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now