J
Jenny
Hi guys,
Ive been getting this error alot of later and looked at a
few knowledge base articles but it still seems to be
occuring would someone please be able to help me???
thx
Jenny
![Smile :) :)](/styles/default/custom/smilies/smile.gif)
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:".
Following recovery steps will 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.
[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.
Ive been getting this error alot of later and looked at a
few knowledge base articles but it still seems to be
occuring would someone please be able to help me???
thx
Jenny
![Smile :) :)](/styles/default/custom/smilies/smile.gif)
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:".
Following recovery steps will 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.
[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.