tombstone server help!
craigibc
some real trouble. We have five sites. The FSMO is on the main DC. We can
replicate any changes from that server to all others. The other four servers
can replicate changes to each other but not to the main DC. I ran dcdiag the
other day and got tombstone errors. I do not know what to do from here. I
will paste a copy of dcdiag report for you.... 1server is the main DC and I
ran dcdiag on the main DC. All other servers return to errors.
craigibc
C:\>dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: CO\1SERVER
Starting test: Connectivity
......................... 1SERVER passed test Connectivity
Doing primary tests
Testing server: CO\1SERVER
Starting test: Replications
REPLICATION-RECEIVED LATENCY WARNING
COSERVER: Current time is 2006-01-20 09:12:14.
DC=ForestDnsZones,DC=wj,DC=test-one,DC=k12,DC=oh,DC=us
Last replication recieved from 7SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 6SERVER at 2005-10-25 08:55:38.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 5SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 4FINDER at 2005-10-25 07:56:06.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 3SERVER at 2005-10-25 05:56:10.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
DC=DomainDnsZones,DC=wj,DC=test-one,DC=k12,DC=oh,DC=us
Last replication recieved from 7SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 6SERVER at 2005-10-25 08:55:38.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 5SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 4FINDER at 2005-10-25 07:56:06.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 3SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
CN=Schema,CN=Configuration,DC=wj,DC=test-one,DC=k12,DC=oh,DC=u
s
Last replication recieved from 7SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 6SERVER at 2005-10-25 08:55:38.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 5SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 4FINDER at 2005-10-25 07:56:06.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 3SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 2GHOST at 2005-10-25 05:48:03.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
CN=Configuration,DC=wj,DC=test-one,DC=k12,DC=oh,DC=us
Last replication recieved from 7SERVER at 2005-10-25 05:56:08.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 6SERVER at 2005-10-25 08:55:38.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 5SERVER at 2005-10-25 05:56:08.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 4FINDER at 2005-10-25 08:54:24.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 3SERVER at 2005-10-25 05:56:08.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 2GHOST at 2005-10-25 05:55:23.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
DC=wj,DC=west-jefferson,DC=k12,DC=oh,DC=us
Last replication recieved from 7SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 6SERVER at 2005-10-25 08:55:38.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 5SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 4FINDER at 2005-10-25 08:55:17.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 3SERVER at 2005-10-25 05:56:09.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Last replication recieved from 2GHOST at 2005-10-25 05:53:10.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
REPLICATION-RECEIVED LATENCY WARNING
Source site:
CN=NTDS Site
Settings,CN=NW,CN=Sites,CN=Configuration,DC=wj,DC=test-one,DC=k12,DC=oh,DC=us
Current time: 2006-01-20 09:12:14
Last update time: 2005-10-25 05:53:34
Check if source site has an elected ISTG running.
Check replication from source site to this server.
REPLICATION-RECEIVED LATENCY WARNING
Source site:
CN=NTDS Site
Settings,CN=MS,CN=Sites,CN=Configuration,DC=wj,DC=test-one,DC=k12,DC=oh,DC=us
Current time: 2006-01-20 09:12:14
Last update time: 2005-10-25 05:53:55
Check if source site has an elected ISTG running.
Check replication from source site to this server.
REPLICATION-RECEIVED LATENCY WARNING
Source site:
CN=NTDS Site
Settings,CN=HS,CN=Sites,CN=Configuration,DC=wj,DC=test-one,DC=k12,DC=oh,DC=us
Current time: 2006-01-20 09:12:14
Last update time: 2005-10-25 08:24:06
Check if source site has an elected ISTG running.
Check replication from source site to this server.
REPLICATION-RECEIVED LATENCY WARNING
Source site:
CN=NTDS Site
Settings,CN=FREY,CN=Sites,CN=Configuration,DC=wj,DC=test-one,DC=k12,DC=oh,DC=us
Current time: 2006-01-20 09:12:14
Last update time: 2005-10-25 05:48:09
Check if source site has an elected ISTG running.
Check replication from source site to this server.
......................... 1SERVER passed test Replications
Starting test: NCSecDesc
......................... 1SERVER passed test NCSecDesc
Starting test: NetLogons
......................... 1SERVER passed test NetLogons
Starting test: Advertising
......................... 1SERVER passed test Advertising
Starting test: KnowsOfRoleHolders
......................... 1SERVER passed test KnowsOfRoleHolders
Starting test: RidManager
......................... 1SERVER passed test RidManager
Starting test: MachineAccount
......................... 1SERVER passed test MachineAccount
Starting test: Services
......................... 1SERVER passed test Services
Starting test: ObjectsReplicated
......................... 1SERVER passed test ObjectsReplicated
Starting test: frssysvol
......................... 1SERVER passed test frssysvol
Starting test: frsevent
......................... 1SERVER passed test frsevent
Starting test: kccevent
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:37
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:37
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:38
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:38
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:38
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:38
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:38
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:38
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:38
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:38
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:38
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:38
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:38
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:38
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:38
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:38
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:42
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:42
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:42
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:42
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:42
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:42
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:42
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:42
Event String: The attempt to establish a replication link for
An Error Event occured. EventID: 0xC00007FA
Time Generated: 01/20/2006 08:59:42
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000785
Time Generated: 01/20/2006 08:59:42
Event String: The attempt to establish a replication link for
......................... 1SERVER failed test kccevent
Starting test: systemlog
......................... 1SERVER passed test systemlog
Starting test: VerifyReferences
......................... 1SERVER 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 : wj
Starting test: CrossRefValidation
......................... wj passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... wj passed test CheckSDRefDom
Running enterprise tests on : wj.test-one.k12.oh.us
Starting test: Intersite
......................... wj.test-one.k12.oh.us passed test Inter
site
Starting test: FsmoCheck
......................... wj.test-one.k12.oh.us passed test FsmoC
heck
C:\>
Kevin D. Goodknecht Sr. [MVP]
> We have a problem that I was not able to solve and now I think that I
> have some real trouble. We have five sites. The FSMO is on the main
> DC. We can replicate any changes from that server to all others. The
> other four servers can replicate changes to each other but not to the
> main DC. I ran dcdiag the other day and got tombstone errors. I do
> not know what to do from here. I
> will paste a copy of dcdiag report for you.... 1server is the main DC
> and I ran dcdiag on the main DC. All other servers return to errors.
Once a DC has been tombsoned it is too late to fix replication problems on
that server and restart replication. How you aproach this is to decide which
DC has the correct infomation, this one or the others, and which you are
going to keep.
You said this is your main DC, what is running on this DC besides the FSMO
roles, is Exchange in use?
Is this a single domain forest?
Do all the other DCs report this one as being tombstoned?
Are they replicating properly?
Use dcdiag /e /v on all DCs.
--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
Ace Fekay [MVP]
Kevin D. Goodknecht Sr. [MVP] <ad...@nospam.WFTX.US> stated, which I
commented on below:
> Once a DC has been tombsoned it is too late to fix replication
> problems on that server and restart replication. How you aproach this
> is to decide which DC has the correct infomation, this one or the
> others, and which you are going to keep.
> You said this is your main DC, what is running on this DC besides the
> FSMO roles, is Exchange in use?
> Is this a single domain forest?
> Do all the other DCs report this one as being tombstoned?
> Are they replicating properly?
>
> Use dcdiag /e /v on all DCs.
Kevin,
Other than a force demotion of Server1 or just yanking it off the network
(assuming the other servers are replicating to each other normally), and
performing a metadata cleanup of Server1's info out of AD, then a
re-promotion (not too bad to do that), there's actually a possibility of
saving it. I just found this out a few days ago. On all DCs enter create
this reg key and restart the netlogon service on all DCs.
Of course I am assuming, since the poster was nice enough to post the
dcdiag, but not any Event ID errors (which would have been equally helpful),
they are getting Event ID 2042's, 2023, 1398, 1988, 1864, or similar errors.
===============================
Force DC replication of a tombstoned DC
One each DC:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Create a REG_DWORD value called:
"Allow Replication With Divergent and Corrupt Partner"
Enter value of 1.
Restart Netlogon
Then force replication in Sites and Services. If there are multiple Sites,
you'll have to wait for your configured schedule for this to propagate to
all DCs. We must keep in mind however, that whatever caused this, it
happened back before Oct 25 (according to the dcdiag). The replication
issues MUST be addressed or replication errors will continue and cause these
errors again.
Once completed and you've insured replication is occuring, return the value
in Allow Replication With Divergent and Corrupt Partner to 0 to not allow it
to replicate outdated data.
Event IDs possibily associated with: Event ID 2042's, 2023, 1398, 1988,
1864, NTFRS, NTDS, or similar errors.
Event ID 2042: It has been too long since this machine replicated:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Operations/34c15446-b47f-4d51-8e4a-c14527060f90.mspx
Active Directory Inside Out (5 of 10): DNS Features and Configuration (First
Question):
http://www.microsoft.com/technet/community/chats/trans/windowsnet/wnet_111204.mspx
Things to consider when a Windows Server 2003-based domain controller or a
Windows 2000-based domain controller runs in a virtual environment (VPC or
VMWare):
http://support.microsoft.com/?id=888794
===============================
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, if I may suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx, you can easily find your post, track
threads, cross-post, and sort by date, poster's name, watched threads or
subject.
Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================
Jorge de Almeida Pinto [MVP]
lingering objects as these might exist!
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto #
MVP Windows Server - Directory Services
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
-----------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNa...@hotmail.com> wrote in
message news:%23TVoJ0f...@TK2MSFTNGP09.phx.gbl...
Ace Fekay [MVP]
Jorge de Almeida Pinto [MVP]
<SubstituteThisWithMyF...@gmail.com> stated, which I
commented on below:
> but before allowing replication to occur (as Ace mentioned), FIRST
> cleanup lingering objects as these might exist!
Forgot about that! I guess we can put that in as the first step right before
creating the reg entry.
Ace
craigibc
Every site has multiple DC's. I will run dcdiag /e /v and will report back
to you. It does seems to be a problem only with the first site. If I create
an object at any site but the first site it will successfully replicate to
all other sites but the first site.
I will run the test and get back with you.
craigibc