Dears,

I have two Domain controllers installed between to sites, when I run repadmin /replsum the data collection for replication summer will show me operation encountered a database error, I thing this issue related to NTDS database corrupted, kindly any advice for solution. based on my search I have found recommended to see log files for 467 for NTDS corrupted, if the NTDS database corrupted how can I fixed?

Thanks..

Hi

 the best solution is to demote this DC and promote it again(Also will do metadata cleanup,make sure all ADDS,DNS,DFS,AD Site and services records updated),but first check which dc is fsmo roles holder.Run "netdom query fsmo" if the broken dc is fsmo roles holder,you could transfer fsmo roles to other dc.

Sieze fsmo roles

https://support.microsoft.com/en-us/kb/255504

Metadata cleanup

https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

Also if you have a succesfull backup,you should restore from this backup.

Note:i recommned that you could demote this broken dc,and promote it again.

When I create user from one domain the other domain controller can't see the new user, do you think the problem with NTDS database?

If replication is broken between the two DCs, then you'll see issues like this.  Your DCs are probably on different versions of the database.  Did you follow the suggestion from Burak?

Hi

 replication summer will show me operation encountered a database error>>> so,your DC's could not replicate succesfully,also could not update DB.As i recommned that demote the this broken dc and promote it again.

hi can you check do you have any event for event id 13568 in file replication log?

Source: NtFrs

Type: Error

Description: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Replica root path is   : "c:\winnt\sysvol\domain" Replica root volume is : "\\.\C:" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons. [1] Volume "\\.\C:" has been formatted. [2] The NTFS USN journal on volume "\\.\C:" has been deleted. [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:". Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

• Edited by Purvesh Adua 15 hours 2 minutes ago

How can I demote this broken dc and promote it again, is there any risky for DC? Is this solution will fix the problem?

• Edited by Dana.Kadi 10 hours 0 minutes ago

Hi

 For server 2008 r2 demote

https://technet.microsoft.com/en-us/library/cc771844%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

For server 2012 r2 demote

https://technet.microsoft.com/en-us/library/jj574104.aspx

After demote this problematic DC,you will do metadata cleanup(for this check the link on my previous article)

For promote server 2008 r2

https://technet.microsoft.com/en-us/library/cc733027(v=ws.10).aspx

For promote server 2012 r2

http://kpytko.pl/active-directory-domain-services/adding-additional-domain-controller-windows-server-2012/

So you have 2 Domain Controller,means have redundancy.But i recommend that you could full backup of DC before demote.

 Usually this method fix the NTDS db issues.

Note:Before run "netdom query fsmo" for check which dc is fsmo roles holder.If this problematic DC is the fsmo holder,you need to transfer fsmo roles to other dc.(check the link on my previous message for transfer)

Thanks Burak, onther question, when I do force replicate by right click on the domain controller the massage appear it said, "The following error occurred during the attempt to synchronize naming context ***.Com from domain XXX.Com to domain controller ZZZ.Com, the replication operation encountered a database error" kindly any advice?

Hi

 Check this artilce for "Replication error 8451 The replication operation encountered a database error"

https://technet.microsoft.com/en-us/library/replication-error-8451-the-replication-operation-encountered-a-database-error%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396