| Event Id | 12292 |
| Source | SAM |
| Description | There are two or more objects that have the same account name attribute in the SAM database. The Distinguished Name of the account is <account name>. 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. |
| Event Information | 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. This information from some newsgroup may help you: ------------------------------------------------------------------------------ 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. Depending on the network topology, this problem can also be caused by Active Directory replication issues between two or more servers. Verify that AD is replicating correctly and check in Sites and Services to ensure that the links are all there between the domain controllers. Assuming replication is happening correctly, manually verify that the account is not showing on any global catalog or AD servers in general. If that does not work, look for |
| Reference Links | More Information Replication Collisions in Windows 2000 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.