I have a Win 2003 R2 SP2 server which is my DC, file server, Exchange server, etc with about 75 XP clients attached to it. Since January I have been seeing event ID 13568 (attached) logged in the File Replication Service event log after every reboot. We had a few problems last year after installing a new AV package on the server where it hung on several occasions and I had to force a reset. I suspect this is what may have caused the problem.
I recently promoted another DC in the domain for testing purposes. On this server I'm seeing event ID 13508 logged in the File Replication Service event log:-
The File Replication Service is having trouble enabling replication from \\server01.rowse.local to VIRTUALSERVER01 for c:\windows\sysvol\domain using the DNS name \\server01.rowse.local. FRS will keep retrying.
The domain is working OK. I have attached the results of a dcdiag and netdiag. The only error in the dcdiag relates to the FRS error.
So far the only solutions I can see are restoring the system state from a tape backup from before the error occured (scary). Or carrying out an Authoritative FRS restore using the BurFlags registry key (also scary).
From reading KB 290762 (http://support.microsoft.com/kb/290762/
) it appears that an Authoritative restore might fix the problem, however I have also read posts on EE from poor people who have lost their domain after carrying out a restore.
I want appreciate any advice on the safest way to move forward.