Ntfrs Journal Wrap Error
- From: "Bill Glidden" <billyg1943@xxxxxxxxxxx>
- Date: Tue, 5 Aug 2008 14:43:25 +1000
I am trying to get a Windows 2003 SBS SP1server to replicate to a newly
added Server 2003 SP2 Domain Controller. Replication has stalled. The
source server has the following error in the File Replication Service Event
Log:
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 05/08/2008
Time: 12:32:41 PM
User: N/A
Computer: HPS001
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:\windows\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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This server had a crash recently and CHKDSK found errors on the disk The
server seems healthy except for the above errors
I made the suggested registry entry and stopped and started the service but
it has not fixed the error.
The destination server has the following error (multiple times) in the File
Replication Service Event Log:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 5/08/2008
Time: 1:30:43 PM
User: N/A
Computer: MIGRATIONDC
Description:
The File Replication Service is having trouble enabling replication from
HPS001 to MIGRATIONDC for c:\windows\sysvol\domain using the DNS name
HPS001.herzigprosser.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name HPS001.herzigprosser.local
from this computer.
[2] FRS is not running on HPS001.herzigprosser.local.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d5 04 00 00 Õ...
Not sure where to go from here. Anyone?
.
- Follow-Ups:
- Re: Ntfrs Journal Wrap Error
- From: Bill Glidden
- Re: Ntfrs Journal Wrap Error
- Prev by Date: Re: suggestions on network storage
- Next by Date: Re: Ntfrs Journal Wrap Error
- Previous by thread: SBS 2003 BOSD (mrxdav.sys), Help Needed Please
- Next by thread: Re: Ntfrs Journal Wrap Error
- Index(es):
Relevant Pages
|
