File replication service error event id 13508

Viewed 29k times. Improve this question. Mike Mike 1 1 gold badge 4 4 silver badges 15 15 bronze badges. Ugh, FRS sucks. I mean, really sucks. That's the first thing I'd try, because FRS just doesn't work and is such a massive pain to fix that it's best to not use it if at all possible. Add a comment. Active Oldest Votes. Verify the Domain Membership of the DC. Verify the DC can communicate with other DCs. Verify the DC can replicate with other DCs.

Verify the replication permissions are correct. Improve this answer. HostBits HostBits This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

Data: 00 00 00 Join our community to see this answer! Unlock 1 Answer and 13 Comments. Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial. What do I get with a subscription? You will be taken to the Create new Basic Task wizard, and the options to run the task based on the event you have selected will be pre-populated. So you can walk many of the wizard pages. If the DC is the only DC in a site, that might not be acceptable.

Skip to main content. This browser is no longer supported. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.

If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. The re-addition will trigger a full tree sync for the replica set. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

Type the value name exactly as shown above. I'd resolve any issues first if possible. I don't like to introduce new DCs when the domain isn't healthy. Does that seem like a good plan? I'm sort of an AD noob so I guess I'd appreciate some validation on that. I'm not sure you'll have another option.