CHR1S Posted March 9, 2012 Posted March 9, 2012 Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13508 Date: 08/03/2012 Time: 17:01:25 User: N/A Computer: DC2 Description: The File Replication Service is having trouble enabling replication from DC1 to DC2 for c:\windows\sysvol\domain using the DNS name DC1.UK. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name DC1.UK from this computer. [2] FRS is not running on DC1.UK. [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. Ive checked DNS, I can ping each DC from the other, I can ping the DCs GUIs. FRS is running as the other DFS shares are replicating successfully too. DCdiag only fails on FRSevent (as above) The sysvols on each DC most certainly dont match! HELP!!
FN-GM Posted March 9, 2012 Posted March 9, 2012 Are the IP settings correct on both DCs? I assume you have tried a reboot? Can you see the Servers DNS records in DNS (check the DNS on both servers)
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 DNS looks fine, replicates correctly too. Tried reboots, tried service restarts (frs) Event Type: Information Event Source: NtFrs Event Category: None Event ID: 13516 Date: 09/03/2012 Time: 11:25:26 User: N/A Computer: DC2 Description: The File Replication Service is no longer preventing the computer DC2 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL. Still no replication
Brpilot99 Posted March 9, 2012 Posted March 9, 2012 Have you tried to access each server from the other using the dns name rather than the IP? Could point to a DNS problem if IP works but DC1.UK etc doesnt !!
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 Replmon says all replications were successfull on both DCs Both servers can see each other by IP/DNS name/GUI name FRS error message keeps being thrown up on DC2 only
Brpilot99 Posted March 9, 2012 Posted March 9, 2012 Silly I know but have you checked that there is plenty of space on both sysvol drives? Also .. try copying and pasting a file from one dc to the others sysvol folder and vice versa .. might show up a permissions problem ..
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 (edited) New error - Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13561 Date: 09/03/2012 Time: 12:07:09 User: N/A Computer: DC1 Description: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Replica root path is : "c:\winnt\sysvol\domain" Replica root volume is : "\\.\C:" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. [1] Volume "\\.\C:" has been formatted. [2] The NTFS USN journal on volume "\\.\C:" has been deleted. [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:". Following recovery steps will be taken to automatically recover from this error state. [1] At the first poll which will occur in 5 minutes this computer will be deleted from the replica set. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. After creating the reg value to auto fix I get this error - Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13560 Date: 09/03/2012 Time: 12:07:10 User: N/A Computer: DC1 Description: The File Replication Service is deleting this computer from the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from the error state, Error status = FrsErrorSuccess At the next poll, which will occur in 5 minutes, this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. For more information, see Help and Support Center at Events and Errors Message Center: Basic Search. Edited March 9, 2012 by CHR1S
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 Event Type: Information Event Source: NtFrs Event Category: None Event ID: 13554 Date: 09/03/2012 Time: 12:12:10 User: N/A Computer: DC1 Description: The File Replication Service successfully added the connections shown below to the replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" "DC2.UK" "DC2.UK" Is that fixed then? lol
Brpilot99 Posted March 9, 2012 Posted March 9, 2012 The second one is not an error its just a warning that DC1 is being deleted from the replica set and then re-added to it. It will also trigger a full tree replication process to sync all server replications sets including hopefully your sysvol ... 1
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 I "think" its fixed, I created a test folder on one DC and it replicated almost immediatly to the other. Going to monitor and see how it goes. Thanks for the support guys
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 Erm, spoke too soon! All GPO application on PCs is now failing because its looking for two policies which dont exist.
Brpilot99 Posted March 9, 2012 Posted March 9, 2012 Does it tell you which policies its looking for .. if so can you check and see if they actually exist ... Check with GPO manager on both servers just in case theres still a replication issue
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 (edited) AD and GPOs are identical over doth DCs, The two missing GPOs are just long GUID strings so I have no way of knowing what they are. I have a hunch that these are ADMX files and the repair has messed with my schema. Might rerun adprep from the server 2008 R2 disk and repopulate my ADMX files again. Edited March 9, 2012 by CHR1S
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 Currently restoring all missing GPO Policies from backup... 3 so far, grrr
CHR1S Posted March 9, 2012 Author Posted March 9, 2012 Yes exactly as I thought, the check and fix procedure restored it to an older state, I restored it from a backup and there seem to be no more errors "touch wood"! Thanks again all
ccp Posted March 9, 2012 Posted March 9, 2012 Hi Chris, Just out of interest (I know you have solved this now so just a question out of curiosity) Are both Servers in the same site and are they located in the same location?
Bruce123 Posted April 11, 2012 Posted April 11, 2012 (edited) Currently restoring all missing GPO Policies from backup... 3 so far, grrr Glad you got it sorted, in my experience FRS can be hard to fix when replication stops working on 2000/2003. They are easier to fix in 2008/2008 R2. Can I ask how you recovered GPOs without restoring the whole of ADS? I know that you can backup GPOs with a right-click in Group Policy Management Console, but can this be automated? Or can you recover individual GPOs from the System State backup taken from a DC? Regards, Bruce. Edited April 11, 2012 by Bruce123
chazzy2501 Posted April 11, 2012 Posted April 11, 2012 I would have done a file level restore and looked for the guid strings of the GPOs and plonked them back into the sysvol. I assume that would work? OR I would have found the GPOs in group policy management and removed them from there (if they were unimportant. Would my approach work?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now