Solved

Event ID 12292

Posted on 2004-08-24
6
1,677 Views
Last Modified: 2008-02-07
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
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 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.
0
Comment
Question by:lemontee
  • 2
6 Comments
 
LVL 15

Expert Comment

by:Yan_west
ID: 11880908
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.
0
 
LVL 15

Accepted Solution

by:
Yan_west earned 250 total points
ID: 11880917
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."
0
 

Expert Comment

by:Jasqid
ID: 22893849
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. )
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
In this article, I show you step by step with screenshots to assist you - HOW TO: Deploy and Install the VMware vCenter Server Appliance 6.5 (VCSA 6.5), with some helpful tips along the way.
This video discusses moving either the default database or any database to a new volume.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now