none
8451 The replication encountered a database error

    Question

  • Hi folks,

    I've 6 DCs in my environment, two of them aren't replicating since 31\10\2016.

    We've 3 DCs in one site, DC1,DC2,DC3.

    Every time I try to replicate DC2 with DC3 and DC1 I got the following error message

    "8451 The replication encountered a database error"

    But the case is different for DC3 as when I try to replicate, I got the following error message

    "The target principal is incorrect".

    Any recommendations?

    Thanks in Advance,

    Mohamed Waly

    Wednesday, December 7, 2016 12:48 PM

All replies

  • Hi

     Check this for "Troubleshooting AD Replication error 8451: The replication operation encountered a database error"

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

    The target principal is incorrect>>>means broken secure channel on the DC3,you should check the article;

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


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

    Wednesday, December 7, 2016 12:52 PM
  • Already tried and none of them works.
    Wednesday, December 7, 2016 1:55 PM
  • Hi,
    Regarding the error 8451, please check the following article to have a try if it helps:
    AD Replication Issue | Event ID 2108 and 1084 | 8451 The replication operation encountered a database error.
    https://lakshmanavn.wordpress.com/2014/10/27/ad-replication-issue-event-id-2108-and-1084-8451-the-replication-operation-encountered-a-database-error/
    Regarding error “The target principal is incorrect”, you could check the following article step by step:
    “THE TARGET PRINCIPAL NAME IS INCORRECT”: ACTIVE DIRECTORY DOMAIN CONTROLLER REPLICATION ISSUE
    https://neilbryan.ca/the-target-principal-name-is-incorrect-active-directory-domain-controller-replication-issue/
    Please Note: Since the web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, December 8, 2016 6:19 AM
    Moderator
  • Already tried and none of them works.

    Inadditon to wendy's shared article after reset password on problematic dc,then you should verfiy port accesibilty between all DC's.You can check this with PortQryUI;

    https://www.microsoft.com/en-us/download/details.aspx?id=24009

    And also if the 8451 error could not be fixed the easiest method just forcefully demote this DC from domain,will do a 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


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

    Thursday, December 8, 2016 6:58 AM