On two of our 2003 domain controllers we were seeing an intermittently 1083 warning followed immediately by a 1955 information event in the Directory Service long at a rate of once or twice on month. Neither DCdiag nor repadmin return any errors. After working with Microsoft support they confirmed this is an expected transient error which can be safely ignored.
Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1083
Date: 4/15/2013
Time: 8:44:57 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: <DC>
Description:
Active Directory could not update the following object with changes received from the domain controller at the following network address because Active Directory was busy processing information.
Object:
<Object>
Network address:
<Address>
Event Type: Information
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1955
Date: 4/15/2013
Time: 8:44:57 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: <DC>
Description:
Active Directory encountered a write conflict when applying replicated changes to the following object.
Object:
<Object>
Time in seconds:
0
Event log entries preceding this entry will indicate whether or not the update was accepted.
A write conflict can be caused by simultaneous changes to the same object or simultaneous changes to other objects that have attributes referencing this object. This commonly occurs when the object represents a large group with many members, and the functional level of the forest is set to Windows 2000. This conflict triggered additional retries of the update. If the system appears slow, it could be because replication of these changes is occurring.
User Action
Use smaller groups for this operation or raise the functional level to Windows Server 2003.
No comments:
Post a Comment