Announcement

Collapse
No announcement yet.

One of my site is not replicating

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

  • One of my site is not replicating

    Hello Team,

    I have one of my site is not replicating..
    even I do a manual replication or netlmon.. i just not doing it. even though in the log showing that replicate successfully but no change was effected.


    >>satus as of: 2/7/2011 3:43:41 PM
    Server is current through Property Update USN: 1689597
    The last replication attemp was successfully. this took place at: 2/7/2011 3:29 PM (LOCAL)


    eventhough though the logs suggested that replication was successfully.. but it's not.

    Thanks,
    HN

  • #2
    Re: One of my site is not replicating

    Hi,

    create a test user and then check if you are able to see it on another dc. Any errors in event view, repadmin /syncall
    Thanks & Regards
    v-2nas

    MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
    Sr. Wintel Eng. (Investment Bank)
    Independent IT Consultant and Architect
    Blog: http://www.exchadtech.blogspot.com

    Show your appreciation for my help by giving reputation points

    Comment


    • #3
      Re: One of my site is not replicating

      I change the user profile like name etc.. but it's not replicating..
      EDIT: when I check the event view on the local server.. I got error.. I think this server is tombstone. Im going to dcpromo it down and dcpromo it back up.

      "Active Directory Replication encountered the existence of objects in the following partition that have been deleted from the local domain controllers (DCs) Active Directory database. Not all direct or transitive replication partners replicated in the deletion before the tombstone lifetime number of days passed. Objects that have been deleted and garbage collected from an Active Directory partition but still exist in the writable partitions of other DCs in the same domain, or read-only partitions of global catalog servers in other domains in the forest are known as "lingering objects".

      This event is being logged because the source DC contains a lingering object which does not exist on the local DCs Active Directory database. This replication attempt has been blocked.

      The best solution to this problem is to identify and remove all lingering objects in the forest.


      Source DC (Transport-specific network address):
      443f12da-3eef-4849-8047-a2c6b5e276fa._msdcs.xx.xxx
      Object:
      CN=xxx\0ACNF:80cebadb-cbc9-4784-bde9-edd7fa4386cc,OU=xxx,OU=xxx,OU=Crossroads,OU=xxx and xxx,DC=xxx,DC=xxx
      Object GUID:
      80cebadb-cbc9-4784-bde9-edd7fa4386cc

      User Action:

      Remove Lingering Objects:

      The action plan to recover from this error can be found at http://support.microsoft.com/?id=314282.

      If both the source and destination DCs are Windows Server 2003 DCs, then install the support tools included on the installation CD. To see which objects would be deleted without actually performing the deletion run "repadmin /removelingeringobjects <Source DC> <Destination DC DSA GUID> <NC> /ADVISORY_MODE". The eventlogs on the source DC will enumerate all lingering objects. To remove lingering objects from a source domain controller run "repadmin /removelingeringobjects <Source DC> <Destination DC DSA GUID> <NC>".

      If either source or destination DC is a Windows 2000 Server DC, then more information on how to remove lingering objects on the source DC can be found at http://support.microsoft.com/?id=314282 or from your Microsoft support personnel.

      If you need Active Directory replication to function immediately at all costs and don't have time to remove lingering objects, enable loose replication consistency by unsetting the following registry key:

      Registry Key:
      HKLM\System\CurrentControlSet\Services\NTDS\Parame ters\Strict Replication Consistency

      Replication errors between DCs sharing a common partition can prevent user and compter acounts, trust relationships, their passwords, security groups, security group memberships and other Active Directory configuration data to vary between DCs, affecting the ability to log on, find objects of interest and perform other critical operations. These inconsistencies are resolved once replication errors are resolved. DCs that fail to inbound replicate deleted objects within tombstone lifetime number of days will remain inconsistent until lingering objects are manually removed by an administrator from each local DC.

      Lingering objects may be prevented by ensuring that all domain controllers in the forest are running Active Directory, are connected by a spanning tree connection topology and perform inbound replication before Tombstone Live number of days pass.

      For more information, see Help and Support Center at "




      Originally posted by v-2nas View Post
      Hi,

      create a test user and then check if you are able to see it on another dc. Any errors in event view, repadmin /syncall
      Last edited by Humannetwork; 7th February 2011, 23:11.

      Comment


      • #4
        Re: One of my site is not replicating

        DCPROMO is a lot of work if it is indeed Tombstoned. Have a read of Post 4 at the following link. http://forums.petri.com/showthread.p...ght=tombstoned

        Don't forget to change the setting back once you have obtained Replication again.
        1 1 was a racehorse.
        2 2 was 1 2.
        1 1 1 1 race 1 day,
        2 2 1 1 2

        Comment


        • #5
          Re: One of my site is not replicating

          I've done before I see your post. I appreciate your help..

          If we change the registry and force the DC to replicate with a good DC, how about the bad database on the tombstone DC? would it replicate the bad databse to good database?

          I just took the safety precaustion, by force it to dcpromo and reintroduce back to the domain.

          Thanks,
          HN

          Originally posted by biggles77 View Post
          DCPROMO is a lot of work if it is indeed Tombstoned. Have a read of Post 4 at the following link. http://forums.petri.com/showthread.p...ght=tombstoned

          Don't forget to change the setting back once you have obtained Replication again.

          Comment


          • #6
            Re: One of my site is not replicating

            Why do you call it a bad database on the old DC? If it is bad as in corrupted then it should be blown away. However if it is bad as in outdated then from my experience in using the modified Registry key it will resync the AD database with the up to date version and untombstone the old DC.

            Remember that each DC has a copy of the AD database and the USN (Updated Sequence Number) will/should not allow old data to overwrite current data. The untombstoned DC will have its out of date information updated during the now possible replication from the higher USN database. Does that make sense?
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment


            • #7
              Re: One of my site is not replicating

              It does make sense with your explaination..
              Everytime I have tombstone DC I always do dcpromo /forceremoval to prevent corrupted database to replicate the a good DB.
              I never thought about the USN. and you are correct. the latest DB will override the old DB.
              nexttime I will use regedit method to fix the issue it's quicker. I have over 80 DCs. Im prety sure I will see a few tombstone DCs in the future.

              Thanks,
              HN

              Originally posted by biggles77 View Post
              Why do you call it a bad database on the old DC? If it is bad as in corrupted then it should be blown away. However if it is bad as in outdated then from my experience in using the modified Registry key it will resync the AD database with the up to date version and untombstone the old DC.

              Remember that each DC has a copy of the AD database and the USN (Updated Sequence Number) will/should not allow old data to overwrite current data. The untombstoned DC will have its out of date information updated during the now possible replication from the higher USN database. Does that make sense?

              Comment

              Working...
              X