Domain replication failing

Hi there,

Im getting an error showing up lots in the event logs for my domain controllers,

------------------------------------------------------------------------------------------------------------------------------
Event Type:      Error
Event Source:      NTDS Replication
Event Category:      Replication
Event ID:      2042
Date:            2/13/2008
Time:            10:48:20 AM
User:            NT AUTHORITY\ANONYMOUS LOGON
Computer:      CASTOR
Description:
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine's views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2006-10-09 01:58:05
Invocation ID of source:
04a3f6c8-f6b8-04a3-0100-000000000000
Name of source:
677941bb-5ace-4b9b-8ec7-e742c52f5c77._msdcs.waikatolink.co.nz
Tombstone lifetime (days):
60
 
The replication operation has failed.
 
User Action:
 
Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:
 
1. Demote or reinstall the machine(s) that were disconnected.
2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
 Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------------------------------------------------------------

Does anyone know how to solve it? the TechNet article says to run repadmin /removelingeringobjects but i dont know how to use it and when i run it it says invalid syntax, any help would be much appreciated

Thanks
Luke
LVL 8
static-voidAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jay_Jay70Commented:
how long did you have that DC turned off for mate? Your quickest solution is going to be a forceremovel, clean, and repromotion
0
static-voidAuthor Commented:
i havent had the dcs turned off, so far as i knew they were functioning fine, how do i go about doing that?
0
Jay_Jay70Commented:
well you can play around with netdom but i wouldnt  bother

on the DC in question (the dead one) just check the dates on the sysvol folder for me - need to see if its a deff problem and not a false alarm...also check replmon and see what she says

if its for real ill guide you through killing and rebuilding it
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

static-voidAuthor Commented:
\\domain\sysvol\domain hasnt been modified since early 07 but policies folder under that has been modified this week
0
Jay_Jay70Commented:
can you run a dcdiag for me please?
0
static-voidAuthor Commented:
Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: SMSSite\CASTOR
      Starting test: Connectivity
         ......................... CASTOR passed test Connectivity

Doing primary tests

   Testing server: SMSSite\CASTOR
      Starting test: Replications
         [Replications Check,CASTOR] A recent replication attempt failed:
            From POLLUX to CASTOR
            Naming Context: DC=ForestDnsZones,DC=Domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 11:46:35.
            The last success occurred at 2006-10-09 01:58:05.
            555 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From FILESERVER to CASTOR
            Naming Context: DC=ForestDnsZones,DC=Domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 11:46:35.
            The last success occurred at 2006-10-09 01:58:05.
            561 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From FILESERVER to CASTOR
            Naming Context: DC=DomainDnsZones,DC=Domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 11:46:35.
            The last success occurred at 2006-10-09 01:58:05.
            555 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From POLLUX to CASTOR
            Naming Context: DC=DomainDnsZones,DC=Domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 11:46:35.
            The last success occurred at 2006-10-09 01:58:05.
            555 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From POLLUX to CASTOR
            Naming Context: CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=n
z
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 11:46:35.
            The last success occurred at 2006-10-09 01:58:05.
            555 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From FILESERVER to CASTOR
            Naming Context: CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=n
z
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 11:46:35.
            The last success occurred at 2006-10-09 01:58:05.
            555 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From POLLUX to CASTOR
            Naming Context: CN=Configuration,DC=Domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 11:48:18.
            The last success occurred at 2006-10-09 02:06:42.
            1416 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From FILESERVER to CASTOR
            Naming Context: CN=Configuration,DC=Domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:20:09.
            The last success occurred at 2006-10-09 02:07:03.
            1546 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From POLLUX to CASTOR
            Naming Context: DC=Domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:31:31.
            The last success occurred at 2006-10-09 02:07:12.
            39468 failures have occurred since the last success.
         [Replications Check,CASTOR] A recent replication attempt failed:
            From FILESERVER to CASTOR
            Naming Context: DC=Domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:32:05.
            The last success occurred at 2006-10-09 02:07:14.
            23624 failures have occurred since the last success.
         REPLICATION-RECEIVED LATENCY WARNING
         CASTOR:  Current time is 2008-02-13 12:33:02.
            DC=ForestDnsZones,DC=Domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 01:58:05.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from POLLUX at 2006-10-09 01:58:05.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=DomainDnsZones,DC=Domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 01:58:05.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from POLLUX at 2006-10-09 01:58:05.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Schema,CN=Configuration,DC=Domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 01:58:05.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from POLLUX at 2006-10-09 01:58:05.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Configuration,DC=Domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 02:07:03.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from POLLUX at 2006-10-09 02:06:45.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=Domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 02:07:14.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from POLLUX at 2006-10-09 02:07:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

         ......................... CASTOR passed test Replications
      Starting test: NCSecDesc
         ......................... CASTOR passed test NCSecDesc
      Starting test: NetLogons
         ......................... CASTOR passed test NetLogons
      Starting test: Advertising
         ......................... CASTOR passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... CASTOR passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... CASTOR passed test RidManager
      Starting test: MachineAccount
         ......................... CASTOR passed test MachineAccount
      Starting test: Services
         ......................... CASTOR passed test Services
      Starting test: ObjectsReplicated
         ......................... CASTOR passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... CASTOR passed test frssysvol
      Starting test: frsevent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... CASTOR failed test frsevent
      Starting test: kccevent
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:20:09
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:20:27
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:26:25
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:30:27
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:31:31
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:32:05
            (Event String could not be retrieved)
         ......................... CASTOR failed test kccevent
      Starting test: systemlog
         ......................... CASTOR passed test systemlog
      Starting test: VerifyReferences
         ......................... CASTOR passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : Domain
      Starting test: CrossRefValidation
         ......................... Domain passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Domain passed test CheckSDRefDom

   Running enterprise tests on : Domain.co.nz
      Starting test: Intersite
         ......................... Domain.co.nz passed test Intersite
      Starting test: FsmoCheck
         ......................... Domain.co.nz passed test FsmoCheck
0
Jay_Jay70Commented:
that is on the dead DC yeah? its had it :)
0
static-voidAuthor Commented:
you sure thats supposed to be my PDC and replication *appears* to be working, when i look at the domain everything looks correct and up to date. Im getting similar errors on my other 2 domain controllers... they cant all be dead as the domain seems to be working fine
0
Jay_Jay70Commented:
no PDC's these days :) it take it it holds your FSMO roles?

basically its lost sync with the other DC's and some time agao - event log and DCDIAG confirms it
0
static-voidAuthor Commented:
but the other 2 DCs seem to have done the same,

this is pollux

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: SMSSite\POLLUX
      Starting test: Connectivity
         ......................... POLLUX passed test Connectivity

Doing primary tests

   Testing server: SMSSite\POLLUX
      Starting test: Replications
         [Replications Check,POLLUX] A recent replication attempt failed:
            From CASTOR to POLLUX
            Naming Context: DC=ForestDnsZones,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:58:03.
            The last success occurred at 2006-10-09 02:01:27.
            559 failures have occurred since the last success.
         [Replications Check,POLLUX] A recent replication attempt failed:
            From FILESERVER to POLLUX
            Naming Context: DC=ForestDnsZones,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:58:04.
            The last success occurred at 2006-10-09 02:01:27.
            565 failures have occurred since the last success.
         [Replications Check,POLLUX] A recent replication attempt failed:
            From FILESERVER to POLLUX
            Naming Context: DC=DomainDnsZones,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:58:03.
            The last success occurred at 2006-10-09 02:01:27.
            559 failures have occurred since the last success.
         [Replications Check,POLLUX] A recent replication attempt failed:
            From CASTOR to POLLUX
            Naming Context: DC=DomainDnsZones,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:58:03.
            The last success occurred at 2006-10-09 02:01:27.
            561 failures have occurred since the last success.
         [Replications Check,POLLUX] A recent replication attempt failed:
            From CASTOR to POLLUX
            Naming Context: CN=Schema,CN=Configuration,DC=domain,DC=co,DC=n
z
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:58:03.
            The last success occurred at 2006-10-09 02:01:27.
            559 failures have occurred since the last success.
         [Replications Check,POLLUX] A recent replication attempt failed:
            From FILESERVER to POLLUX
            Naming Context: CN=Schema,CN=Configuration,DC=domain,DC=co,DC=n
z
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:58:03.
            The last success occurred at 2006-10-09 02:01:27.
            559 failures have occurred since the last success.
         [Replications Check,POLLUX] A recent replication attempt failed:
            From FILESERVER to POLLUX
            Naming Context: CN=Configuration,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:58:03.
            The last success occurred at 2006-10-09 02:07:00.
            1554 failures have occurred since the last success.
         [Replications Check,POLLUX] A recent replication attempt failed:
            From CASTOR to POLLUX
            Naming Context: CN=Configuration,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:58:03.
            The last success occurred at 2006-10-09 02:06:57.
            1361 failures have occurred since the last success.
         [Replications Check,POLLUX] A recent replication attempt failed:
            From FILESERVER to POLLUX
            Naming Context: DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 13:00:58.
            The last success occurred at 2006-10-09 02:09:09.
            23682 failures have occurred since the last success.
         REPLICATION-RECEIVED LATENCY WARNING
         POLLUX:  Current time is 2008-02-13 13:02:23.
            DC=ForestDnsZones,DC=domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 02:01:27.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from CASTOR at 2006-10-09 02:01:27.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=DomainDnsZones,DC=domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 02:01:27.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from CASTOR at 2006-10-09 02:01:27.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Schema,CN=Configuration,DC=domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 02:01:27.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from CASTOR at 2006-10-09 02:01:27.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Configuration,DC=domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 02:07:00.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from CASTOR at 2006-10-09 02:06:57.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=domain,DC=co,DC=nz
               Last replication recieved from FILESERVER at 2006-10-09 02:09:09.

               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

         ......................... POLLUX passed test Replications
      Starting test: NCSecDesc
         ......................... POLLUX passed test NCSecDesc
      Starting test: NetLogons
         ......................... POLLUX passed test NetLogons
      Starting test: Advertising
         ......................... POLLUX passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... POLLUX passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... POLLUX passed test RidManager
      Starting test: MachineAccount
         ......................... POLLUX passed test MachineAccount
      Starting test: Services
         ......................... POLLUX passed test Services
      Starting test: ObjectsReplicated
         ......................... POLLUX passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... POLLUX passed test frssysvol
      Starting test: frsevent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... POLLUX failed test frsevent
      Starting test: kccevent
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:52:10
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:54:02
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:58:03
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:58:03
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:58:03
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:58:03
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:58:03
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:58:04
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   13:00:25
            (Event String could not be retrieved)
         ......................... POLLUX failed test kccevent
      Starting test: systemlog
         ......................... POLLUX passed test systemlog
      Starting test: VerifyReferences
         ......................... POLLUX passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : domain
      Starting test: CrossRefValidation
         ......................... domain passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... domain passed test CheckSDRefDom

   Running enterprise tests on : domain.co.nz
      Starting test: Intersite
         ......................... domain.co.nz passed test Intersite
      Starting test: FsmoCheck
         ......................... domain.co.nz passed test FsmoCheck

and this is fileserver --------------------------------------------------------------------------------------------------

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: SMSSite\FILESERVER
      Starting test: Connectivity
         ......................... FILESERVER passed test Connectivity

Doing primary tests

   Testing server: SMSSite\FILESERVER
      Starting test: Replications
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From CASTOR to FILESERVER
            Naming Context: DC=ForestDnsZones,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:07:12.
            551 failures have occurred since the last success.
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From POLLUX to FILESERVER
            Naming Context: DC=ForestDnsZones,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:07:13.
            551 failures have occurred since the last success.
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From POLLUX to FILESERVER
            Naming Context: DC=DomainDnsZones,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:07:12.
            551 failures have occurred since the last success.
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From CASTOR to FILESERVER
            Naming Context: DC=DomainDnsZones,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:07:12.
            553 failures have occurred since the last success.
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From POLLUX to FILESERVER
            Naming Context: CN=Schema,CN=Configuration,DC=domain,DC=co,DC=n
z
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:07:12.
            551 failures have occurred since the last success.
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From CASTOR to FILESERVER
            Naming Context: CN=Schema,CN=Configuration,DC=domain,DC=co,DC=n
z
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:07:12.
            551 failures have occurred since the last success.
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From POLLUX to FILESERVER
            Naming Context: CN=Configuration,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:07:12.
            1385 failures have occurred since the last success.
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From CASTOR to FILESERVER
            Naming Context: CN=Configuration,DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:07:12.
            1310 failures have occurred since the last success.
         [Replications Check,FILESERVER] A recent replication attempt failed:
            From POLLUX to FILESERVER
            Naming Context: DC=domain,DC=co,DC=nz
            The replication generated an error (8614):
            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.
            The failure occurred at 2008-02-13 12:59:46.
            The last success occurred at 2006-10-09 02:09:36.
            39602 failures have occurred since the last success.
         REPLICATION-RECEIVED LATENCY WARNING
         FILESERVER:  Current time is 2008-02-13 13:07:15.
            DC=ForestDnsZones,DC=domain,DC=co,DC=nz
               Last replication recieved from POLLUX at 2006-10-09 02:07:13.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from CASTOR at 2006-10-09 02:07:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=DomainDnsZones,DC=domain,DC=co,DC=nz
               Last replication recieved from POLLUX at 2006-10-09 02:07:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from CASTOR at 2006-10-09 02:07:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Schema,CN=Configuration,DC=domain,DC=co,DC=nz
               Last replication recieved from POLLUX at 2006-10-09 02:07:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from CASTOR at 2006-10-09 02:07:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            CN=Configuration,DC=domain,DC=co,DC=nz
               Last replication recieved from POLLUX at 2006-10-09 02:07:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

               Last replication recieved from CASTOR at 2006-10-09 02:07:12.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

            DC=domain,DC=co,DC=nz
               Last replication recieved from POLLUX at 2006-10-09 02:09:36.
               WARNING:  This latency is over the Tombstone Lifetime of 60 days!

         ......................... FILESERVER passed test Replications
      Starting test: NCSecDesc
         ......................... FILESERVER passed test NCSecDesc
      Starting test: NetLogons
         ......................... FILESERVER passed test NetLogons
      Starting test: Advertising
         ......................... FILESERVER passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... FILESERVER passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... FILESERVER passed test RidManager
      Starting test: MachineAccount
         * FILESERVER is not trusted for account delegation
         The corresponding flag bits are missing from the computer object's
         User-Account-Control attribute. You can re-run this command and
         include the /FixMachineAccount option to attempt a repair.
         ......................... FILESERVER failed test MachineAccount
      Starting test: Services
            NtFrs Service is stopped on [FILESERVER]
         ......................... FILESERVER failed test Services
      Starting test: ObjectsReplicated
         ......................... FILESERVER passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... FILESERVER passed test frssysvol
      Starting test: frsevent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... FILESERVER failed test frsevent
      Starting test: kccevent
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:56:42
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:58:45
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:59:46
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:59:46
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:59:46
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:59:46
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:59:46
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:59:46
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:59:46
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 02/13/2008   12:59:46
            (Event String could not be retrieved)
         ......................... FILESERVER failed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 02/13/2008   13:00:58
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 02/13/2008   13:00:59
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 02/13/2008   13:00:59
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 02/13/2008   13:00:59
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 02/13/2008   13:01:08
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 02/13/2008   13:01:09
            (Event String could not be retrieved)
         ......................... FILESERVER failed test systemlog
      Starting test: VerifyReferences
         ......................... FILESERVER passed test VerifyReferences

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : domain
      Starting test: CrossRefValidation
         ......................... domain passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... domain passed test CheckSDRefDom

   Running enterprise tests on : domain.co.nz
      Starting test: Intersite
         ......................... domain.co.nz passed test Intersite
      Starting test: FsmoCheck
         ......................... domain.co.nz passed test FsmoCheck
-------------------------------------------------------------------------------------------------------------------

what does that mean? how can i fix it?
0
Jay_Jay70Commented:
actually it looks like they have all headbutted each other...something there is whacked out big time -
http://technet2.microsoft.com/windowsserver/en/library/34c15446-b47f-4d51-8e4a-c14527060f901033.mspx?mfr=true
0
static-voidAuthor Commented:
ok is there anything i can do to get around this? ive looked at that and im not sure what to do in terms of the lingering objects thing, that didnt make much sense to me...
0
Jay_Jay70Commented:
it basically works like this - you have DC's that dont talk, it tombstones them which means they become dead as far as AD is concerned, so it basically annihilates them, you plug it back in and it raises its fingers sayin gi have a record of you, but your not active....too old, and then turns its back

You can remvoe these lingering objects references and make them active again by using the repadmin commands as spoken about in the document
0
static-voidAuthor Commented:
so i want to run
repadmin /removelingeringobjects ServerName ServerGUID DirectoryPartition /advisory_mode

but for the server name and the server ID which server do i use? dont they all have lingeringobjects? should i perfrom that on all 3 DCs? Will i lose data doing this (login details ect)?

thanks
Luke
0
static-voidAuthor Commented:
Ive spawned this part to a new question cause it seems like this is a pretty large problem, answer it in there so i can give you some points for it

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_2003_Active_Directory/Q_23160912.html

Thanks
Luke
0
Jay_Jay70Commented:
Hey Luke - sorry mate, the time difference is a killer if you arent in Aus :)

You will want to run that command on all affected DC's
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
static-voidAuthor Commented:
cool that worked like a charm, no more errors. Thanks Heaps for your help, much appreciated aye. do u wanna post your answer above in the other question i made and ill give u sum points 4 it?
0
Jay_Jay70Commented:
Sweet as man - glad we are up and running :)
0
static-voidAuthor Commented:
yeah same those errors were making me nervous but like i said i wasnt actually seeing any effects except error messages, wierd
0
Jay_Jay70Commented:
yah - cant say i have seen that sort of thing happen before - good catch though
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.