Announcement

Collapse
No announcement yet.

replication issue : "The replication generated an error (8606):"

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • replication issue : "The replication generated an error (8606):"

    Hi
    This is the error I'm getting "The replication generated an error (8606):"

    I have 3 DC's two in the same site (same subnet and switch) third is in a remote site.
    This error comes in the main AD (domain master) after running:

    dcdiag /e /q /v /fix > c:\dcdiag.txt

    See full output in attached file.


    It looks like the last replication worked about two months ago:
    "The last success occurred at 2008-07-20 10:51:57. "
    At that date this server had SCSI hardware failure and was down for a few hours.
    Don't know way it did not replicate since and after bringing the server up.
    As I understand if the servers did not replicate for more than 60 days - it's a big issue to resolve.
    Anyway, I need your advice on how to fix this replication issue.

    Thanks!
    Nir
    Attached Files

  • #2
    Re: replication issue : "The replication generated an error (8606):"

    How did you restore it after the SCSI failure?

    Comment


    • #3
      Re: replication issue : "The replication generated an error (8606):"

      You should probably demote the problematic DC and promote it again after making sure all data is cleaned up in AD.

      However, this could cause an issue as some objects might be more up to date on that server than on the other ones. If this isn't a big issue for you, don't research other options, just demote it.

      That's why you should check your logs more than once every 2months
      VCP on vSphere (4), MCITP:EA/DBA, MCTS:Blahblah

      Comment


      • #4
        Re: replication issue : "The replication generated an error (8606):"

        Looks like my bad….
        The server was recovered from acronis image after the SCSI failure.
        Like advised I will need to demote it and re promote it
        I will need to transfer all his roles to DC2;
        DNS, DHCP, print server.
        I wanted to start with moving the "operation master" from the faulty DC to DC2
        But it gives me: "the requested FSMO operation faild. The current FSMO holder could not be contacted"
        I guess it's because this DC is faulty…
        Please advice on how to continue



        is there a best practice for this procedure or step by step?


        thanks

        Comment


        • #5
          Re: replication issue : "The replication generated an error (8606):"

          You can not restore a DC simply from an image. If you do so, you have to do it offline and restore an up to date system state.

          Doing a simple image restore causes USN rollback situations.

          There is a workaround but it is pretty hackish, it involves setting a registry key to make Windows think it was just restored from a system state, and to ignore the current USN - don't do that in production.

          As I said, demote the "bad" DC. Try a dcpromo, it probably will not work.
          Force it, then clean up the metadata in AD. Once everything about the "bad" DC is gone, seize the FSMO roles (seizing lets you "grab" them when the original master is dead...make sure it *NEVER* comes back up though!).

          Then, once you have a single DC with all FSMO roles, promote the second one. Let it replicate. Wait for a little while, make sure everything is fine, then re-distribute your FSMO roles as you see fit.

          Search this forum for info on forcing a demote, FSMO seizing etc, they are pretty common questions and you should find everything you need.
          VCP on vSphere (4), MCITP:EA/DBA, MCTS:Blahblah

          Comment


          • #6
            Re: replication issue : "The replication generated an error (8606):"

            i did as indicated, though the metadata cleanup was successful, when i try to re-introduce it into the domain
            i got an error, after some investigates i found some FSMO leftovers and cleaned them.

            then I re-introduce the faulty DC with dcpromo, it worked OK!
            I gave it a few hours and then add GC to that DC.
            when all looked OK i cleaned the event loges and run:

            dcdiag /e /q /v /fix > c:\dcdiag_new.txt (attached)

            looks OK now...


            thanks for the help.
            Attached Files

            Comment


            • #7
              Re: replication issue : "The replication generated an error (8606):"

              Great !

              Now I'm sure you will check your event logs more than once every 61 days
              VCP on vSphere (4), MCITP:EA/DBA, MCTS:Blahblah

              Comment

              Working...
              X