File Replication issues/errors

  • Thread starter Thread starter DM
  • Start date Start date
D

DM

Hi,

We are running Windows 2000 SBS with Exchange and ISA.
When running DCDiag we get all tests passing except for
the following:

**********************************

Starting test: frssysvol
Error: No record of File Replication System, SYSVOL
start
The Active Directory may be prevented from starting.
......................... SERVER1 passed test frssysvol

**********************************

We are also getting the following error event in the File
Replication event log:

**********************************

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 01/09/2003
Time: 5:23:56 AM
User: N/A
Computer: SERVER1
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:".
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.
[1] At the first poll, which will occur in 5 minutes,
this computer will be deleted from the replica set. 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.
[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.

WARNING: During the recovery process data in the replica
tree may be unavailable. 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.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the
New->DWORD Value function under the Edit Menu item. Type
the value name exactly as shown above.

********************************

I have been unable to find any explanation of this issue
on the support and technet sites...any light on this
situation or course of action would be greatly appreciated.

Regards,

DM
 
FRS is used when there are multiple domain controllers to keep SYSVOL in
sync across all the DCs. FRS uses the USN journal to keep track of changes
made on a local volume and to determine which changes need to be propagated
to the other members in the replica. This journal is of finite size, and
every file operation can create an entry or multiple entries. If the FRS
service is stopped or can't keep up with the changes, the journal will run
out of space and wrap back to the beginning, hence the term "journal wrap."
This KB article should give you some more information.

http://support.microsoft.com/default.aspx?scid=kb;en-us;292438

If you have only one DC, then there's no need to keep SYSVOL in sync with
the rest of the DCs because there are none. In this sense, you could simply
ignore the journal wrap as it is causing you no harm. However, if you do
decide to add another DC (say a backup DC to your SBS PDC), the new BDC
won't be able to sync up SYSVOL until the journal wrap issue is resolved on
your SBS PDC. You could cross that bridge when you get to it. So, if you
have only one DC, you could theoretically leave the FRS service stopped and
ignore any references to journal wrap errors.

On a side note, FRS is used for DFS replicas as well as SYSVOL. If you have
DFS replicas, you won't want to stop FRS (in the case you have only one DC).

--Richard

This posting is provided "AS IS" with no warranties, and confers no rights.

DM said:
Hi,

We are running Windows 2000 SBS with Exchange and ISA.
When running DCDiag we get all tests passing except for
the following:

**********************************

Starting test: frssysvol
Error: No record of File Replication System, SYSVOL
start
The Active Directory may be prevented from starting.
......................... SERVER1 passed test frssysvol

**********************************

We are also getting the following error event in the File
Replication event log:

**********************************

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 01/09/2003
Time: 5:23:56 AM
User: N/A
Computer: SERVER1
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:".
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.
[1] At the first poll, which will occur in 5 minutes,
this computer will be deleted from the replica set. 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.
[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.

WARNING: During the recovery process data in the replica
tree may be unavailable. 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.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the
New->DWORD Value function under the Edit Menu item. Type
the value name exactly as shown above.

********************************

I have been unable to find any explanation of this issue
on the support and technet sites...any light on this
situation or course of action would be greatly appreciated.

Regards,

DM
Click to expand...
 
Back
Top