I’m having a rather big problem which I can’t figure out. The problem is File Replication Service. PLEASE READ ON! 
I’m running a school network domain, with over 600 users. There are about 10 servers running Windwos Server 2003 Std., 2 of thsoe are Domain Controllers.
We had some rather unfortunate problems, we lost the power (with faling UPS!!!!). This resulted in the NTDS database being corrupted on BOTH DCs. NETLOGON and SYSVOL disapeared on both domain controllers.
My PDC is called Ares and my other DC is Zeus.
I read a MS article about temporarily stabilized SYSVOL. I had to Edit “HKEY_LOCAL_MACHINE\SYSTEM
ameters” and change DWORD SYSVOLREADY to 1 or 2, making NETLOGON and SYSVOL reappear. And then coping all the scipts and policies in the %systemroot%\SYSVOL.
This attemp did make NETLOGON and SYSVOL reapear, but the FRS still reported problems (Ares is having problems with ZEUS and visaversa). I also found several Experts-exchange links, but none that helped me.
I also used an MS article on how to rebuild the SYSVOL tree and its content and re-creating junctions, but without any fixes to my problem. http://support.microsoft.com/default.aspx?scid=kb;en-us;315457
I then took a backup of my %sytemroot%\SYSVOL. I then demoted ZEUS to a normal member server, and promoted it again. I then got EventID 13508 (http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=NtFrs&phase=1
), and event ID 13565.
After promoting ZEUS again, I demoted ARES, but this did not fix anything. I still got the same problems. On Both domain controllers event logs saying that %servername% can’t become a DC before SYSVOL and NETLOG has been replicated (event ID 13565), followed by event log 13508 (same as above). It told me to way till it had replicated troughout the domain (which it always says when adding a new DC), I let the server alone for 24 hours, but only returned to get 13508 event erros. NETLOGON and NTFRS services have no problems starting.
I’m using DELL PowerEdge 2600 & 2800 servers, so the hardware is no problem.
The strange part, while having this FRS problems, demoting and promoting the DCs didn’t report any errors. After promoting, the servers did not have any problems adding a replicaset in “Sites and Trusts” under NTDS, and when forcing a replication the message “%servername% has replicated its connections” returns.
I also tested AD by adding users on Ares, and checking on ZEUS. This worked. I then disabled the users and change the properties on ZUES and checked on ARES. This worked. No problems transferring FSMOs etc. either.
It seems that I’m only having a problem with Replication on “file-level” if can call it that. FRS!
I also tried some tools located on the server 2003 CD, NLTEST, DcDiag and NetDiag.
DcDiag returning some DcGetDcName and some Adverticing problems on Ares, and ZEUS returing FRS problems.
After I demoted Ares, Zeus became my PDC, which isnt a big deal, that will be correted WHEN or IF I get this up and running again.
There are shouldn’t be any DNS problems in my domain. I can ping names and FQDNs without problems. I believe all the correct SRV, A host and other records are in the DNS. 99,99999999% sure! :) Checked this with a hundred times!
I’m an educated IT-professional, but I’m down on my knees with this one. I need help. I can’t afford to do a clean install with over 600 users on the domain! No way! :)
Sorry for this long and boring essay! Plz ask if you don’t understand part of the description! :)