C
Castelfidardo
4 windows server 2003 (no R2) domain controllers 2 sites 2 DCs at each site.
1 DC in each site uses FRS to replicate folders (user documents mainly) over
the WAN between sites. Approximately 50 GB of data. 200000 files in 12
replicated folders.
A few weeks ago, the administrator noticed problem with replication. He said
new files were replicated OK, and older modified files not.
Unaware of the consequences, he followed the advice in one of the event
viewer error messages details on one of the DCs
…..
net stop ntfrs
(rd /s /q c:\windows\ntfrs\jet
net start ntfrs
….
Replication restarted, several NTRFS_Preexisted directories appeared, a lot
of _NTFS_nnn files and directories under the SYSVOL share, WAN links
overloaded, volumes almost to full space use. I guess that with this
procedure he got the replication started from scratch but he probably missed
or ignored other tasks that should have been performed before or after the
mentioned workaround and it were n't mentioned on the event viewer detail.
The present situation is: In ONE DC the FRS starts y after a while crashes
(now is disabled)
NTFRS messages on evet viewer
Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13501
Date: 10/14/2009
Time: 3:26:59 PM
Description:
The File Replication Service is starting.
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/14/2009
Time: 3:29:17 PM
Description:
The File Replication Service is having trouble enabling replication from
SRo1 to SBu1 for e:\folder1\folder2 using the DNS name Sro1.domain.local. FRS
will keep retrying.
Following are some of the reasons you would see this warning….
Followed by two more event for two more replicated folders (not shown here)
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13506
Date: 10/14/2009
Time: 3:49:58 PM
Description:
The File Replication Service failed a consistency check
(!"Invalid CO Location cmd transition-1")
in "JrnlUpdateChangeOrder:" at line 4393.
The File Replication Service will restart automatically at a later time. If
this problem persists a subsequent entry in this event log describes the
recovery procedure.
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13555
Date: 10/14/2009
Time: 3:49:58 PM
Description:
The File Replication Service is in an error state. Files will not replicate
to or from one or all of the replica sets on this computer until the
following recovery steps are performed…
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13504
Date: 10/14/2009
Time: 3:51:32 PM
User: N/A
Computer: SRVBSAS01
Description:
The File Replication Service stopped without cleaning up.
Tools run on servers:
Netdiag: OK en 4 DCs
Dcdiag /e Everything OK except references to errors on frsevent frssysvol
Gpotool: A few policies out of sync (different version on AD that on sysvol)
Questions:
1 Is it possible (or advisable) try to repair the NTFSR so that replication
do not have to be configure from scratch? He would not like to replicate 50
GB over that WAN link…
2. In any case (repair and go on, or repair and configure from zero) which
is the procedure to be followed.
3. Or is it advisable to open a support case with MS?
Thanks in advance.
1 DC in each site uses FRS to replicate folders (user documents mainly) over
the WAN between sites. Approximately 50 GB of data. 200000 files in 12
replicated folders.
A few weeks ago, the administrator noticed problem with replication. He said
new files were replicated OK, and older modified files not.
Unaware of the consequences, he followed the advice in one of the event
viewer error messages details on one of the DCs
…..
net stop ntfrs
(rd /s /q c:\windows\ntfrs\jet
net start ntfrs
….
Replication restarted, several NTRFS_Preexisted directories appeared, a lot
of _NTFS_nnn files and directories under the SYSVOL share, WAN links
overloaded, volumes almost to full space use. I guess that with this
procedure he got the replication started from scratch but he probably missed
or ignored other tasks that should have been performed before or after the
mentioned workaround and it were n't mentioned on the event viewer detail.
The present situation is: In ONE DC the FRS starts y after a while crashes
(now is disabled)
NTFRS messages on evet viewer
Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13501
Date: 10/14/2009
Time: 3:26:59 PM
Description:
The File Replication Service is starting.
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 10/14/2009
Time: 3:29:17 PM
Description:
The File Replication Service is having trouble enabling replication from
SRo1 to SBu1 for e:\folder1\folder2 using the DNS name Sro1.domain.local. FRS
will keep retrying.
Following are some of the reasons you would see this warning….
Followed by two more event for two more replicated folders (not shown here)
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13506
Date: 10/14/2009
Time: 3:49:58 PM
Description:
The File Replication Service failed a consistency check
(!"Invalid CO Location cmd transition-1")
in "JrnlUpdateChangeOrder:" at line 4393.
The File Replication Service will restart automatically at a later time. If
this problem persists a subsequent entry in this event log describes the
recovery procedure.
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13555
Date: 10/14/2009
Time: 3:49:58 PM
Description:
The File Replication Service is in an error state. Files will not replicate
to or from one or all of the replica sets on this computer until the
following recovery steps are performed…
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13504
Date: 10/14/2009
Time: 3:51:32 PM
User: N/A
Computer: SRVBSAS01
Description:
The File Replication Service stopped without cleaning up.
Tools run on servers:
Netdiag: OK en 4 DCs
Dcdiag /e Everything OK except references to errors on frsevent frssysvol
Gpotool: A few policies out of sync (different version on AD that on sysvol)
Questions:
1 Is it possible (or advisable) try to repair the NTFSR so that replication
do not have to be configure from scratch? He would not like to replicate 50
GB over that WAN link…
2. In any case (repair and go on, or repair and configure from zero) which
is the procedure to be followed.
3. Or is it advisable to open a support case with MS?
Thanks in advance.