none
Active Directory Replication Issue

    Question

  • Dears,

    I'm getting below error on Primary Domain Controller after installing additional domain controller.

    "8451 The replication operation encountered a database error."

    We have installed additional domain controller but after installing we were getting  below error in event viewer for additional domain controller.

    "The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed."

    I have checked couple of article and it seems it can only be fixed with database repair.

    Please advise.

    Regards,
    Hakim. B



    Hakim.B Sr.System Administrator

    Thursday, February 23, 2017 7:41 AM

All replies

  • Dear Hakim,

    You don't need to repair the database. First try to move the database from one location to another location.

    eg:- From C: drive to D drive. This will fix the issue.

    To do the database movement, Please find the below link.

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

    Thanks

    Syed Abdul Kadar M.


    Dont forget to mark as Answered if you found this post helpful.

    Thursday, February 23, 2017 7:48 AM
  • Hi

     For error 8451 refer to this article;

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

    Otherwise you should share "dcdiag" result from problematic DC.


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur


    Thursday, February 23, 2017 7:48 AM
  • Dear Syed,

    Thanks for prompt reply..

    I m wondering how moving the database will solve the issue.

    Regards,

    Hakim. B



    Hakim.B Sr.System Administrator

    Thursday, February 23, 2017 8:07 AM
  • Dear Burak,

    Thanks for prompt reply.

    I will send the DCdiag result in few minutes.

    Regards,

    Hakim. B


    Hakim.B Sr.System Administrator

    Thursday, February 23, 2017 8:07 AM
  • Dear Hakim,

    I had the similar issue in two of  my domain controllers which where located on different branch location. I had the similar database error, first I tried to demote and promote it again no change.  

    At last I moved the database to different location it worked very charm. I did the same for the other domain controller as well.

    So far both DC's are very healthy :)

    Thanks

    Syed Abdul Kadar M.


    Dont forget to mark as Answered if you found this post helpful.

    Thursday, February 23, 2017 9:10 AM
  • Dear Syed,

    Instead of moving the database can i run the chkdsk /f and check.

    I think this will fix it also.

    Regards,

    Hakim. B


    Hakim.B Sr.System Administrator

    Thursday, February 23, 2017 9:46 AM
  • Dear Hakim,

    Yes you can.

    Thanks

    Syed Abdul Kadar M.


    Dont forget to mark as Answered if you found this post helpful.

    Thursday, February 23, 2017 10:13 AM
  • Hi,

    I moved the database to different location but still facing same issue.

    Regards,

    Hakim. B


    Hakim.B Sr.System Administrator

    Wednesday, March 1, 2017 5:43 PM
  • Hi

     For error 8451 refer to this article;

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

    Otherwise you should share "dcdiag" result from problematic DC.


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur




    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Wednesday, March 1, 2017 7:29 PM
  • Dear Burak,

    Please share your email address so I will send you directly the dcdiag result.

    Regards,
    hakim. B


    Hakim.B Sr.System Administrator

    Thursday, March 2, 2017 7:02 AM
  • Please upload results on OneDrive;

    https://onedrive.live.com/


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Thursday, March 2, 2017 9:13 AM
  • I have uploaded the dcdiag logs.

    https://ufile.io/0b044

    Please download the file from above link.


    Regards,
    hakim. B


    Hakim.B Sr.System Administrator

    Sunday, March 5, 2017 8:08 AM
  • First;

    SRVNCBDC04 has not finished initializing. >>> This ADC has sync issues with a Writable DC.So first verfiy the port accesbility between this dc and other's.Then if the issue persist just forcefully demote SRVNCBC04 will perform metadata cleanup and promote it as domain controller again.

    Metadata cleanup;https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx?f=255&mspperror=-2147217396

    SRVNCPDC01 >>> What is this Server OS?If it's Server 2012,you cn skip DFS error log's.But older than server 2012 you should fix the DFS issues,check the article

    https://support.microsoft.com/en-us/help/2958414/dfs-replication-how-to-troubleshoot-missing-sysvol-and-netlogon-shares

    Note: First try to fix the issue on Srv04 then perfrom steps on srv01 cause this is your PDC and holds fsmo roles also before perform steps on srv01 you should transfer&seize fsmo roles any other healthy dc.(if necessary)

    https://support.microsoft.com/en-us/help/255504/using-ntdsutil.exe-to-transfer-or-seize-fsmo-roles-to-a-domain-controller


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Sunday, March 5, 2017 11:16 AM