A
Armick
Looking for some assistance on the following:
Getting an directory replication error 1084 (see below) on a DC during
normal replication where updates to a specific user object are not being
accepted by a specific DC (works fine everywhere else). This is now
logjamming all directory replication for all other sites for this DC.
Searches relate to errors derived from universal groups or forestprep
related issues (253644 & 326855) none of which apply in this case.
Attempts to view the OU where the affected user object is placed from the DC
using ADUC generates an operations failure preventing the user list from
being generated. All other user objects appear to be listed fine. Next
steps we have are to take the server down and test database consistency from
DS Restore Mode using NTDSUTIL. Any other ideas on what we can do to
resolve the issue?
TIA,
A
Replication error: The directory replication agent (DRA) couldn't update
object CN="username",OU=Users,OU=User
Accounts,OU=Cityname,DC=gowlings,DC=corp (GUID
68a054d9-dbc1-4cc4-82db-31a68525b843) on this system with changes which have
been received from source server
5d3b3f95-40bd-4e9c-9674-5f96027d5e1c._msdcs.domain.com. An error occurred
during the application of the changes to the directory database on this
system.
The error message is:
The replication operation encountered a database error.
The directory will try to update the object later on the next replication
cycle. Synchronization of this server with the source is effectively blocked
until the update problem is corrected.
If this condition appears to be related to a resource shortage, please stop
and restart this Windows Domain Controller.
If this condition is an internal error, a database error, or an object
relationship or constraint error, manual intervention will be required to
correct the database and allow the update to proceed. It is valuable to note
that the problem is caused by the fact that the change on the remote system
cannot be applied locally. Manually updating the objects on the local system
in not recommended. Instead, on the source system (which has the changes
already), try to reverse or back out the change. Then, on the next
replication cycle, observe whether the change can now be applied locally.
The record data is the status code.
Getting an directory replication error 1084 (see below) on a DC during
normal replication where updates to a specific user object are not being
accepted by a specific DC (works fine everywhere else). This is now
logjamming all directory replication for all other sites for this DC.
Searches relate to errors derived from universal groups or forestprep
related issues (253644 & 326855) none of which apply in this case.
Attempts to view the OU where the affected user object is placed from the DC
using ADUC generates an operations failure preventing the user list from
being generated. All other user objects appear to be listed fine. Next
steps we have are to take the server down and test database consistency from
DS Restore Mode using NTDSUTIL. Any other ideas on what we can do to
resolve the issue?
TIA,
A
Replication error: The directory replication agent (DRA) couldn't update
object CN="username",OU=Users,OU=User
Accounts,OU=Cityname,DC=gowlings,DC=corp (GUID
68a054d9-dbc1-4cc4-82db-31a68525b843) on this system with changes which have
been received from source server
5d3b3f95-40bd-4e9c-9674-5f96027d5e1c._msdcs.domain.com. An error occurred
during the application of the changes to the directory database on this
system.
The error message is:
The replication operation encountered a database error.
The directory will try to update the object later on the next replication
cycle. Synchronization of this server with the source is effectively blocked
until the update problem is corrected.
If this condition appears to be related to a resource shortage, please stop
and restart this Windows Domain Controller.
If this condition is an internal error, a database error, or an object
relationship or constraint error, manual intervention will be required to
correct the database and allow the update to proceed. It is valuable to note
that the problem is caused by the fact that the change on the remote system
cannot be applied locally. Manually updating the objects on the local system
in not recommended. Instead, on the source system (which has the changes
already), try to reverse or back out the change. Then, on the next
replication cycle, observe whether the change can now be applied locally.
The record data is the status code.