Event ID 1864

Hi,

I receive the following error message on the DC. We only run 1 DC so there is no need for replication. How can i remove those replication objects?

The local domain controller has not recently received replication information from a number of domain controllers.   The count of domain controllers is shown, divided into the following intervals.
 
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
1
Tombstone lifetime (days):
180
 Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
 
To identify the domain controllers by name, install the support tools included on the installation  CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest.   The command is "repadmin /showvector /latency <partition-dn>".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
LVL 1
ktpoitmAsked:
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.

BrianIT ManagerCommented:
Did you ever have another DC?  If so it looks like it may have not been removed properly.   Here is a link to remove a DC that is no longer functional.  http://support.microsoft.com/kb/216498

Thanks,
Brian
0
ktpoitmAuthor Commented:
Hi thx for the answer. Yes we had 3 Domain Controller before, but there is only one DC in the metadata.
So unfortunately that is not the problem

Thx
Sebastian
0
BrianIT ManagerCommented:
Sebastian,
Run the following command from the cmd prompt to see if it tells you who the culprit is:
repadmin /replsum /errorsonly >> c:\temp\readmin_err.txt

Thanks,
Brian
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

ktpoitmAuthor Commented:
i ran the command and the output is as followed :
Replication Summary Start Time: 2008-11-12 10:04:58



Beginning data collection for replication summary, this may take awhile:

  ....





Source DC           largest delta  fails/total  %%  error





Destination DC    largest delta    fails/total  %%  error

Assertion


0
BrianIT ManagerCommented:
Well that is a wealth of info. :)  It did complete correct?

Brian
0
ktpoitmAuthor Commented:
it did not give me any error message :P. It seems like the DC tries to replicated with an non existing server. Would it help if i rebuild the second Domain Controller move everything over to it and rebuild DC1, or would that move the Problem?
0
BrianIT ManagerCommented:
I'm not 100% sure on that but it would seem that it would move the problem since that really isn't doing anything to remove the issue.
0
ktpoitmAuthor Commented:
Do you have any idea how to resolve the issue?
0
BrianIT ManagerCommented:
My next step would be to search though AD using LDP to see if I could find anything.  That is going to take some time though.
0
ktpoitmAuthor Commented:
I just checked ldap and saw some NTDS entries under Lostandfound. Could that have anything to do with it?
0
BrianIT ManagerCommented:
Only if it was the same names as your old DCs.  If you find anything for those old DCs remove it.
0
ktpoitmAuthor Commented:
i ran dcdiag and got the following error. I dont know if that has anything to do with it, im just shooting in the dark right now

  Starting test: VerifyEnterpriseReferences
         The following problems were found while verifying various important DN

         references.  Note, that  these problems can be reported because of

         latency in replication.  So follow up to resolve the following

         problems, only if the same problem is reported on all DCs for a given

         domain or if  the problem persists after replication has had

         reasonable time to replicate changes.
            [1] Problem: Missing Expected Value

             Base Object: CN=LostAndFoundConfig,CN=Configuration,DC=ktpo,DC=ops

             Base Object Description: "Server Object"

             Value Object Attribute: serverReference

             Value Object Description: "DC Account Object"

             Recommended Action: This could hamper authentication (and thus

            replication,  etc).  Check if this server is deleted, and if so

            clean up this DCs Account  Object.  If the problem persists and

            this is not a deleted DC, authoratively restore the DSA object from

            a good copy, for example the DSA on the DSA's home server.

             
            [2] Problem: Missing Expected Value

             Base Object: CN=LostAndFoundConfig,CN=Configuration,DC=ktpo,DC=ops

             Base Object Description: "Server Object"

             Value Object Attribute: serverReference

             Value Object Description: "DC Account Object"

             Recommended Action: This could hamper authentication (and thus

            replication,  etc).  Check if this server is deleted, and if so

            clean up this DCs Account  Object.  If the problem persists and

            this is not a deleted DC, authoratively restore the DSA object from

            a good copy, for example the DSA on the DSA's home server.

             
         ......................... KTPO05DC1 failed test VerifyEnterpriseReferences
0
BrianIT ManagerCommented:
It seems to me that it is saying the objects still exist somewhere in AD.  Since it has been more than 180 days you really can't restore it and remove it again.  It has to be somewhere in the metadata.

Brian
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
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
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.