Re: Need help quick please ! ntfrs errors

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jill Zoeller [MSFT] (jillz_at_online.microsoft.com)
Date: 08/16/04 

Date: Mon, 16 Aug 2004 15:14:33 -0700

I'm not sure what happened to your event text, but I can at least decipher
the event IDs for you below. For info about tshooting FRS, see
http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/dfs/tshootfrs.mspx

13512 (This is informational and doesn't indicate a replication problem)
The File Replication Service has detected an enabled disk write cache on the
drive containing the directory %2 on the computer %1. The File Replication
Service might not recover when power to the drive is interrupted and
critical updates are lost.

13568 (This is a bad one--a journal wrap causes replication to cease. You'll
need to perform a D2 to recover. Journal wraps can be caused by running
Chkdsk--perhaps this is what happened?).
The File Replication Service has detected that the replica set "%1" is in
JRNL_WRAP_ERROR.

Replica set name is: "%1"

Replica root path is: "%2"

Replica root volume is: "%3"

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 "%3" has been formatted.

[2] The NTFS USN journal on volume "%3" has been deleted.

[3] The NTFS USN journal on volume "%3" 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 "%3".

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 %4 minutes, this computer will be
deleted from the replica set. If you do not want to wait %4 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 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.

13501
File Replication Service is starting 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael" <michael@thecomputer.com> wrote in message
news:T7aUc.45209$US4.4119@trndny01...
> Running Windows 2000 Server - I get the following entries in the event log
> approx every 20 min:
>
> Event Type: Warning
> Event Source: NtFrs
> Event Category: None
> Event ID: 13512
> Date: 8/2/2004
> Time: 6:44:44 AM
> User: N/A
> Computer: DOMAIN
> Description:
> The description for Event ID ( 13512 ) in Source ( NtFrs ) cannot be
found.
> The local computer may not have the necessary registry information or
> message DLL files to display messages
>  from a remote computer. You may be able to use the /AUXSOURCE= flag to
> retrieve this description;
> see Help and Support for details. The following information is part of the
> event: DOMAIN , c:\winnt\ntfrs\jet.
>
>
> Event Type: Error
> Event Source: NtFrs
> Event Category: None
> Event ID: 13568
> Date: 8/2/2004
> Time: 6:45:49 AM
> User: N/A
> Computer: DOMAIN
> Description:
> The description for Event ID ( 13568 ) in Source ( NtFrs ) cannot be
found.
> The local computer may not have the necessary registry information or
> message DLL files to display messages
> from a remote computer. You may be able to use the /AUXSOURCE= flag to
> retrieve this description;
> see Help and Support for details.
> The following information is part of the event:
> DOMAIN SYSTEM VOLUME (SYSVOL SHARE), c:\winnt\sysvol\domain, \\.\C:, 5.
>
>
> Event Type: Information
> Event Source: NtFrs
> Event Category: None
> Event ID: 13501
> Date: 8/2/2004
> Time: 6:51:04 AM
> User: N/A
> Computer: DOMAIN
> Description:
> The description for Event ID ( 13501 ) in Source ( NtFrs ) cannot be
found.
> The local computer may not have the necessary registry information or
> message DLL files to display messages
> from a remote computer.
> You may be able to use the /AUXSOURCE= flag to retrieve this description;
> see Help and Support for details. The following information is part of the
> event:
> The event log file is corrupt..
>
>
> This seemed to start after there was a problem with a bad (shared) printer
> driver on the server and it kept rebooting anytime someone tried to print
> to it. I deleted the driver and they now print directly to the networked
> printer which solved the problem, which didn't occur until I upgraded
> BlackICE firewall on the server to the latest version. I think  some file
> or database corruption somewhere might be the cause??. Also, since this
> started happening the workstations will sometimes get booted off the
server
> and the server has to be restarted. Might chkdsk fix it (maybe the USN
> journal needs fixed?)? Can you suggest anything else? I'll be there
> tomorrow early AM.

Relevant Pages

  • Re: Event Error 13568
    ... The File Replication Service has detected that the replica set "DOMAIN ... A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to ... "FRS no longer performs an automatic non-authoritative ...
    (microsoft.public.windows.server.sbs)
  • Re: Event Error 13568
    ... > The File Replication Service has detected that the replica set "DOMAIN ... > File Replication Service was not running on this computer for a long ... You should reset the registry parameter described above to ... "FRS no longer performs an automatic non-authoritative ...
    (microsoft.public.windows.server.sbs)
  • Re: NtFrs Error Message in the Event Log
    ... > replica set "DOMAIN SYSTEM VOLUME " ... > File Replication Service was not running on this computer ... > "Enable Journal Wrap Automatic Restore" ...
    (microsoft.public.windows.server.sbs)
  • Re: "Not enough storage is available to complete this operation" ?
    ... > The File Replication Service has detected that the replica set "DOMAIN ... > SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. ... > A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to ...
    (microsoft.public.win2000.group_policy)
  • Re: Need help quick please ! ntfrs errors
    ... The local computer may not have the necessary registry information or ... message DLL files to display messages ... The File Replication Service might not recover when power to the ...
    (microsoft.public.win2000.file_system)