I have 2 servers that are both DC's and have a replicated fileshare that lost communication for a while (a DNS error I think) and now won't resync. Both servers are running Windows Server 2008 R2 Standard. Server1 is the server that should have the most
up to date files, and I have backups so I'm not worried too much about losing files on Server2.
If I could get some recommendations of how to get the servers back into synch I'd appreciate it.
(Server 1) ActiveDirectory_DomainService Error 1988: Active Directory Domain Services Replication encountered the existence of objects in the following partition that have been deleted from the local domain controllers (DCs) Active Directory Domain Services database. Not all direct or transitive replication partners replicated in the deletion before the tombstone lifetime number of days passed. Objects that have been deleted and garbage collected from an Active Directory Domain Services partition but still exist in the writable partitions of other DCs in the same domain, or read-only partitions of global catalog servers in other domains in the forest are known as "lingering objects".
(Server1) ActiveDirectory_DomainService Error 1863: This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers in this site: 1
(Server1) NtFrs Warning 13508: The File Replication Service is having trouble enabling replication from SERVER2 to SERVER1 for c:\windows\sysvol\domain using the DNS name server2.xxx.xxx. FRS will keep retrying.
(Server2) ActiveDirectory_DomainService Error 1864 (multiple occurrences in 24 hours): This directory server has not recently received replication information 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:1 More than two months:1 More than a tombstone lifetime:1 Tombstone lifetime (days):60
(Server2) ActiveDirectory_DomainService Warning 2093 (multiple occurrences in 24 hours): The remote server which is the owner of a FSMO role is not responding. This server has not replicated with the FSMO role owner recently. Operations which require contacting a FSMO operation master will fail until this condition is corrected. Elapsed time since last successful replication (hours): 3148
(Server2) ActiveDirectory_DomainService Warning 2088: Active Directory Domain Services could not use DNS to resolve the IP address of the source domain controller listed below Alternate server name: server1.xxx.xxx Failing DNS host name: ee9bab52-8c14-4bbe-b1aa-082a53945d5e._msdcs.xxx.xxx
(Server2) DFSR error 5002 (multiple occurrences in 24 hours): The DFS Replication service encountered an error communicating with partner SERVER1 for replication group User Data. Partner DNS address: server1.xxx.xxx Optional data if available: Partner WINS Address: server1 Partner IP Address: xxx.xxx.xx.xx The service will retry the connection periodically. Additional Information: Error: 1825 (A security package specific error occurred.)
(Server2) SRMSVC Warning 12317 (multiple occurrences in 24 hours): File Server Resource Manager failed to enumerate share paths or DFS paths. Mappings from local file paths to share and DFS paths may be incomplete or temporarily unavailable. FSRM will retry the operation at a later time. Context: Domain: MyDomain Error-specific details: Error: DfsMapCacheAdd(Domain), 0x80070005, Access is denied.
(Server2) NtFrs Warning 13508: The File Replication Service is having trouble enabling replication from SERVER1 to SERVER2 for c:\windows\sysvol\domain using the DNS name server1.xxx.xxx. FRS will keep retrying.
(Server2) DFSR warning 14526 (multiple occurrences in 24 hours): DFS could not contact the server1.xxx.xxx Active Directory. DFS will be using cached data. The return code is in the record data.
(Server2) DFSR event 14529 (multiple occurrences in 24 hours): DFS has connected to the server2.xxx.xxx. Active Directory.
Best practices analyzer:
(Server 1&2) The following domain-based namespace meets the prerequisites for using the Windows Server 2008 mode, but is instead using the Windows 2000 Server mode.
(Server 1&2) The File Server Storage Reports Manager service is running even though all reports, file management tasks, and classification rules have finished.
(Server2) There should not be a large number of replication conflicts in the replicated folder ‘share3’
(Server2) There should not be a large number of replication conflicts in the replicated folder ‘share4’
If I could get some recommendations of how to get the servers back into synch I'd appreciate it.
(Server 1) ActiveDirectory_DomainService Error 1988: Active Directory Domain Services Replication encountered the existence of objects in the following partition that have been deleted from the local domain controllers (DCs) Active Directory Domain Services database. Not all direct or transitive replication partners replicated in the deletion before the tombstone lifetime number of days passed. Objects that have been deleted and garbage collected from an Active Directory Domain Services partition but still exist in the writable partitions of other DCs in the same domain, or read-only partitions of global catalog servers in other domains in the forest are known as "lingering objects".
(Server1) ActiveDirectory_DomainService Error 1863: This directory server has not received replication information from a number of directory servers within the configured latency interval. Latency Interval (Hours): 24 Number of directory servers in all sites: 1 Number of directory servers in this site: 1
(Server1) NtFrs Warning 13508: The File Replication Service is having trouble enabling replication from SERVER2 to SERVER1 for c:\windows\sysvol\domain using the DNS name server2.xxx.xxx. FRS will keep retrying.
(Server2) ActiveDirectory_DomainService Error 1864 (multiple occurrences in 24 hours): This directory server has not recently received replication information 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:1 More than two months:1 More than a tombstone lifetime:1 Tombstone lifetime (days):60
(Server2) ActiveDirectory_DomainService Warning 2093 (multiple occurrences in 24 hours): The remote server which is the owner of a FSMO role is not responding. This server has not replicated with the FSMO role owner recently. Operations which require contacting a FSMO operation master will fail until this condition is corrected. Elapsed time since last successful replication (hours): 3148
(Server2) ActiveDirectory_DomainService Warning 2088: Active Directory Domain Services could not use DNS to resolve the IP address of the source domain controller listed below Alternate server name: server1.xxx.xxx Failing DNS host name: ee9bab52-8c14-4bbe-b1aa-082a53945d5e._msdcs.xxx.xxx
(Server2) DFSR error 5002 (multiple occurrences in 24 hours): The DFS Replication service encountered an error communicating with partner SERVER1 for replication group User Data. Partner DNS address: server1.xxx.xxx Optional data if available: Partner WINS Address: server1 Partner IP Address: xxx.xxx.xx.xx The service will retry the connection periodically. Additional Information: Error: 1825 (A security package specific error occurred.)
(Server2) SRMSVC Warning 12317 (multiple occurrences in 24 hours): File Server Resource Manager failed to enumerate share paths or DFS paths. Mappings from local file paths to share and DFS paths may be incomplete or temporarily unavailable. FSRM will retry the operation at a later time. Context: Domain: MyDomain Error-specific details: Error: DfsMapCacheAdd(Domain), 0x80070005, Access is denied.
(Server2) NtFrs Warning 13508: The File Replication Service is having trouble enabling replication from SERVER1 to SERVER2 for c:\windows\sysvol\domain using the DNS name server1.xxx.xxx. FRS will keep retrying.
(Server2) DFSR warning 14526 (multiple occurrences in 24 hours): DFS could not contact the server1.xxx.xxx Active Directory. DFS will be using cached data. The return code is in the record data.
(Server2) DFSR event 14529 (multiple occurrences in 24 hours): DFS has connected to the server2.xxx.xxx. Active Directory.
Best practices analyzer:
(Server 1&2) The following domain-based namespace meets the prerequisites for using the Windows Server 2008 mode, but is instead using the Windows 2000 Server mode.
(Server 1&2) The File Server Storage Reports Manager service is running even though all reports, file management tasks, and classification rules have finished.
(Server2) There should not be a large number of replication conflicts in the replicated folder ‘share3’
(Server2) There should not be a large number of replication conflicts in the replicated folder ‘share4’