Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: NTDS Replication|
A schema mismatch encountered while replicating object CN=domain,CN=,CN=domain,CN=domain,DC=MYDC,DC=MYDC from server ,<server>. A schema sync has been queued and sync on DC CN=Configuration,DC=MYDC,DC=com will be retried after the schema sync.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is NTDS and what are the roles of its components?
You may experience this issue if you install a Windows Server 2003-based domain controller into an existing domain that contains Windows Server 2008-based domain controllers and Microsoft Windows 2000 Server Service Pack 4 (SP4)-based domain controllers. See ME947020 for information on solving this problem.
As per Microsoft: "This problem can occur if schema inconsistency failures occur during synchronization until the schema cache is reloaded". See ME300642 for more details.
From a newsgroup post: "These error messages can be safely ignored. Actually, these messages can occur if the schema is imported in an order other than superclass inheritance. When a class is imported, superclass attributes point to other classes. Since these may not have been imported yet, we may see these errors in the application event log. These errors are common logs which may be added when running ADPrep to upgrade Schema. ME325379 also mentions event ID 1153 logs and specifically states that these logs can be ignored".
|Private comment: Subscribers only. See example of private comment|
|Links: ME300642, ME325379, ME947020|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated