Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replication Problem

Status
Not open for further replies.

BradCustom

IS-IT--Management
Oct 5, 2007
296
US
I have two domain controllers the PDC is a Windows 2000 Advanced Server and the BDC is a WIndows 2003 Server. The power supply died on PDC over the weekend; once backup and running I forgot to reset the system clock. The time reverted back to 2006-01-03; because this server is the time server that time was propagated accross the network. Of course AD Replication took place before I changed the time on the Server to the correct time.

Now I have a SYSVOL replication problem between the two Servers and I'm affraid the only way I can fix it is to use DCPROMO. Below is the REPADMIN for the Windows 2003 Server. I can post the results of other tools if needed.


Code:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.CUSTOM>repadmin /showrepl

repadmin running command /showrepl against server localhost

Default-First-Site-Name\MAINSERVER
DC Options: (none)
Site Options: (none)
DC object GUID: 47dacdae-b692-4418-99cd-475a8d0e4eec
DC invocationID: d14b26b9-0346-45bf-aa42-2b983653db03

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

DC=custom,DC=msft
    Default-First-Site-Name\PRIMSERVER via RPC
        DC object GUID: ccafc5e7-ac84-4b3a-ab48-94d6266bfc5a
        Last attempt @ 2009-02-19 16:53:55 failed, result 8614 (0x21a6):
            The Active Directory cannot replicate with this server because the t
ime since the last replication with this server has exceeded the tombstone lifet
ime.
        671 consecutive failure(s).
        Last success @ 2006-01-03 02:37:55.

CN=Configuration,DC=custom,DC=msft
    Default-First-Site-Name\PRIMSERVER via RPC
        DC object GUID: ccafc5e7-ac84-4b3a-ab48-94d6266bfc5a
        Last attempt @ 2009-02-19 16:53:55 failed, result 8614 (0x21a6):
            The Active Directory cannot replicate with this server because the t
ime since the last replication with this server has exceeded the tombstone lifet
ime.
        399 consecutive failure(s).
        Last success @ 2006-01-03 02:36:25.

CN=Schema,CN=Configuration,DC=custom,DC=msft
    Default-First-Site-Name\PRIMSERVER via RPC
        DC object GUID: ccafc5e7-ac84-4b3a-ab48-94d6266bfc5a
        Last attempt @ 2009-02-19 16:53:55 failed, result 8614 (0x21a6):
            The Active Directory cannot replicate with this server because the t
ime since the last replication with this server has exceeded the tombstone lifet
ime.
        77 consecutive failure(s).
        Last success @ 2006-01-03 02:19:26.

Source: Default-First-Site-Name\PRIMSERVER
******* 669 CONSECUTIVE FAILURES since 2006-01-03 02:37:55
Last error: 8614 (0x21a6):
            The Active Directory cannot replicate with this server because the t
ime since the last replication with this server has exceeded the tombstone lifet
ime.

Thanks for your help!
 
Not sure if this is the best option, but you could probably just demote/promote the 2003 server.


Thanks,
Andrew

[medal] Hard work often pays off over time, but procrastination pays off right now!
 
Thanks,

I mentioned that in my post as a last resort; I'd like to try and fix the problem without using DCPROMO.
 
So you did. My apologies :)

Thanks,
Andrew

[medal] Hard work often pays off over time, but procrastination pays off right now!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top