Event ID 2042 & 1925 = Replication problems

Started work for a new company last week which has a 2003 server domain.
Forest and Domain Functional level is set to 2003.

They have 4 sites throughout the UK all in the same domain and 2003 etc as above.
3 sites replicate back and forth fine.
One site however in London does not replicate.
Can ping the site via netbios and ping from the site to all other sites via netbios.
Below are the event IDs from one of the DCs in one of the sites which is trying to replicate to the London site.

Event Type:      Error
Event Source:      NTDS Replication
Event Category:      Replication
Event ID:      2042
Date:            06/02/2008
Time:            10:10:27
Computer:      DC01
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:
2007-06-27 16:55:52
Invocation ID of source:
Name of source:
Tombstone lifetime (days):
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.


Event Type:      Warning
Event Source:      NTDS KCC
Event Category:      Knowledge Consistency Checker
Event ID:      1925
Date:            06/02/2008
Time:            10:10:27
Computer:      DC01
The attempt to establish a replication link for the following writable directory partition failed.
Directory partition:
Source domain controller:
CN=NTDS Settings,CN=londonserver,CN=Servers,CN=london,CN=Sites,CN=Configuration,DC=domainname,DC=local
Source domain controller address:
Intersite transport (if any):
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=domainname,DC=local
This domain controller will be unable to replicate with the source domain controller until this problem is corrected.  
User Action
Verify if the source domain controller is accessible or network connectivity is available.
Additional Data
Error value:
8614 The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.

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

Any tips or heads up on this appreciated as I have now got to get this corrected pretty quickly, so any tips advice appreciated.
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.

rpartingtonAuthor Commented:
Struggling a bit with this one.

Replication is definately going into the Problem office ie London,
However anyinternal changes on the london dc are not being replicated.

I can Ping back and forth via all DC Netbios and IP addresses both ways

Using the
 the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication.

Showed that it was successful however it also showed that no objects were removed.
can u plese fun mps report tool on one dc on london site and any other site where replication is working fine and upload it on the site, so that it will be a great help to solve the problem
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!

sorry its was not fun its run... :-) a typo
rpartingtonAuthor Commented:
Thanks for that,
However for the time being Ive implemented the Regedit fix just to get allow replication outbound from the london site.

 Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner

We have to join another office to the domain today from a differant part of the country, and I did'nt want to have the london offices new objects only sat at london and not replicated out to the other offices.
I would prefer to get this replication issue fixed 1st rather than just relying on the reg fix as Ive not had chance to double check what happens when I remove the reg setting.
Unfortunately its not my shout and we have to start joining this new office today so it wont be until next week that I can hopefully start checking this replication issue out.
If I get chance by all means I will post the MPS Output today/tomorrow. 7-8th feb

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
rpartingtonAuthor Commented:
Sorry for the delay.
No excuse, I simply forgot about this question.
The above registry fix did the trick.
I implemented it and all is working fine.
I then reverted the reg fix back to how it was previously and it is still working fine.

Again apologies for the delay.
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.