none
result 8451 (0x2103)

    Question

  • Hi

    I can see below error only for domain partition.

    Repadmin: running command /showrepl against full DC localhost

    SDN\DC02

    DSA Options: IS_GC 

    Site Options: (none)

    DSA object GUID: b6044713-e4bb-4793-8b51-fe8346e69d70

    DSA invocationID: 0842ddde-d376-46a8-9042-75e3adc9a0b1



    ==== INBOUND NEIGHBORS ======================================



    DC=IHS,DC=com

        EU07\EU07DC01 via RPC

            DSA object GUID: 053667ff-af7a-4868-bb41-b0b1d5a3d5ba

            Last attempt @ 2017-01-10 13:22:18 failed, result 8451 (0x2103):

                The replication operation encountered a database error.

            51 consecutive failure(s).

            Last success @ (never).

        CA151\CA151DC01 via RPC

            DSA object GUID: 23e863aa-0fac-45eb-a2db-964aee9b4284

            Last attempt @ 2017-01-10 13:22:47 failed, result 8451 (0x2103):

                The replication operation encountered a database error.

            109 consecutive failure(s).

            Last success @ (never).

        CA150\CA150DC01 via RPC

            DSA object GUID: 04416d8b-59c4-4f45-8abe-97d0b2db076b

            Last attempt @ 2017-01-10 13:22:49 failed, result 8451 (0x2103):

                The replication operation encountered a database error.

            116 consecutive failure(s).

            Last success @ (never).

        CA002\CA002DC02 via RPC

            DSA object GUID: 75544cac-83c7-4107-82d2-a333dbebae0d

            Last attempt @ 2017-01-10 13:22:53 failed, result 8451 (0x2103):

                The replication operation encountered a database error.

            238 consecutive failure(s).

            Last success @ (never).

        

    Tuesday, January 10, 2017 1:51 PM

All replies

  • Hi,

    Please troubleshoot this issue with this KB article below:

    Troubleshooting AD Replication error 8451: The replication operation encountered a database error

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

    More specifically, please enable NTDS diagnostic logging for Replication Events and Internal Processing at a level of 5 then analyze logs.

    Best Regards,

    Amy


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

    Wednesday, January 11, 2017 10:46 AM
    Moderator
  • Hi,

    Would you please provide us with an update on the status of your issue?

    Best Regards,

    Amy


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

    Monday, January 23, 2017 3:16 PM
    Moderator
  • still no solution... only decided to demote and promote as no solution did not work of offline and database repair as well..

    Wednesday, February 8, 2017 2:46 PM
  • Even though the KB indicates not to demote and re-promote ( I have no idea what is the reason behind the recommendation), I will prefer exactly that over troubleshooting or repair database any day. Demote (if you still can), or forcefully demote+metadata cleanup, then re-promote is a much quicker, cleaner way for a susceptible database.
    Wednesday, February 8, 2017 4:55 PM
  • I have done repair databse as well but did not helped me
    Wednesday, February 8, 2017 5:17 PM
  • Hi,

    At this point, I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.

    Best Regards,

    Amy


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

    Tuesday, February 14, 2017 2:28 AM
    Moderator