Event Error 1864
Contents |
takes a few minutes. Join Now Hello, We have multiple DCs in different sites, and all five servers but one are showing Event ID
Event Id 1864 Activedirectory_domainservice
1864 in the log: ------------------ This is the replication status for event id 1864 ntds replication the following directory partition on this directory server. Directory partition: DC=ForestDnsZones,DC=domain,DC=domain,DC=org This directory server has not recently received replication information
Event Id 1864 Replication
from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 0 event 1864 activedirectory_domainservice More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 60 ------------ I ran dcdiag and all the tests are passing except the NCSecDesc test. Which also seems to indicate problems with replication. I did some research and read many blogs and articles. Microsoft says that this has to do with RODCs but we don't have any RODCs in this forest. Any repadmin /test:replication ideas or suggestions? Reply Subscribe View Best Answer RELATED TOPICS: Replication Issues Event ID 1864 Replication issue with event id's - 1256,1311,2042,2087,8524 NTDS Replication Event ID 1864   1 2 Next ► 30 Replies Jalapeno OP Moneer81 Aug 10, 2012 at 8:27 UTC oh and I also ran the repadmin /showvector /latency command that the Event 1864 suggests you run but I am not really sure how to read the results. Attached you will see a screenshot of the results. 0 Mace OP Jay6111 Aug 10, 2012 at 8:35 UTC You can ignore the NCSecDesc test if you don't have any RODC's in your environment. This test fails when run from 2008 DC's. If you could run the following command from one of the DC's Dcdiag.exe /e /v >> C:\dcdiag1.txt That produces a text file in the root of C drive called "dcdiag1.txt". Post back here and attach the text document for review. -Jay 0 Jalapeno OP Moneer81 Aug 10, 2012 at 10:38 UTC Thanks Jay. Attached is the dcdiag1.txt. dcdiag1.txt (70 KB) 0 Jalapeno OP Moneer81 Aug 10, 2012 at 10:47 UTC Going
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of
Repadmin /showvector /latency Partition-dn
this site About Us Learn more about Stack Overflow the company Business Learn this directory server has not recently received replication information more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _
Event Id 1862
Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody https://community.spiceworks.com/topic/250336-replication-issues-event-id-1864 can answer The best answers are voted up and rise to the top Windows Server 2003 AD Replication error 1864 up vote 0 down vote favorite Quick question on Active Directory replication. The AD topology is simple: Hub site and 10 Branch sites. I have one connection object between Branch "A" DC and Hub DC in Active Directory Sites and Services. Does it mean that http://serverfault.com/questions/696627/windows-server-2003-ad-replication-error-1864 Branch "A" DC has only one replication partner? If so, why do I see replication error ID 1864 on the Branch "A" DC related to domain controllers in other sites? Event Type: Error Event Source: NTDS Replication Event Category: Replication Event ID: 1864 Date: 6/4/2015 Time: 12:16:08 PM User: NT AUTHORITY\ANONYMOUS LOGON Computer: ABranchDC Description: This is the replication status for the following directory partition on the local domain controller. Directory partition: DC=ForestDnsZones,DC=Company,DC=com 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: 4 More than a week: 3 More than one month: 3 More than two months: 1 More than a tombstone lifetime: 1 Tombstone lifetime (days): 60 I know that there are some DCs in other branch sites that were not properly demoted. Working on that. But I'm curious, why do I see those errors? Only one partition error is shown here, while I'm getting the same error for Configuration, Schema and DomainDnsZones also. active-directory replication share|improve this question asked Jun 4 '15 at 13:54 Vadym Ry
Add-on Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers http://www.eventid.net/display-eventid-1864-source-NTDS%20Replication-eventno-4849-phase-1.htm and workstation via the Splunk Universal Forwarder. read more... Event ID: 1864 Source: NTDS Replication Source: NTDS Replication Type: Error Description:This is the replication status for the following directory partition on the local domain http://kb.eventtracker.com/evtpass/evtPages/EventId_1864_NTDSReplication_47520.asp controller. Directory partition: CN=Schema,CN=Configuration,DC=uu,DC=local 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: event id
information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals. More than 24 hours: 2 More than a week: 2 More than one month: 0 More than two months: 0 More than a tombstone lifetime: 0 Tombstone lifetime (days): 60 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