Event ID 13568 Source NtFrs

Hi Everyone.

While trying to find out the reason that our remote sites aren't picking up
the changes in group policies, I noticed that at our head office the NTFRS
service was set to disabled.

From the event logs, it has been stopped for 2 months. Which explains why no
changes have reached the other sites.

When I started the NTFRS service, there was the expected Event ID 13568.

To get this server back into the replication set, I need to "Enable Journal
Wrap Automatic Restore" in the registry.

Problem is, this server has a whole lot of changes to group policies I have
done over the last week. Will I lose those changes? Is there a way to do
this without losing those changes?



-------------------


Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 31/07/2008
Time: 10:19:56 AM
User: N/A
Computer: WALLTECH-SBS
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.

Hello Bob,

Where also changes made on the site DC during that time? The problem is now
that you can/will end here: http://support.microsoft.com/kb/875495

Personally i would remove the site DC with dcpromo /forceremoval then cleanup
metadata on the main DC and promote it again.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi Everyone.
>
> While trying to find out the reason that our remote sites aren't
> picking up the changes in group policies, I noticed that at our head
> office the NTFRS service was set to disabled.
>
> From the event logs, it has been stopped for 2 months. Which explains
> why no changes have reached the other sites.
>
> When I started the NTFRS service, there was the expected Event ID
> 13568.
>
> To get this server back into the replication set, I need to "Enable
> Journal Wrap Automatic Restore" in the registry.
>
> Problem is, this server has a whole lot of changes to group policies I
> have done over the last week. Will I lose those changes? Is there a
> way to do this without losing those changes?
>
> -------------------
>
> Event Type: Error
> Event Source: NtFrs
> Event Category: None
> Event ID: 13568
> Date: 31/07/2008
> Time: 10:19:56 AM
> User: N/A
> Computer: WALLTECH-SBS
> 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.
>

is that DC the PDC FSMO? When editing GPOs the PDC by default is targeted,
although you can retarget the GPMC.

If yes, in that it is the PDC FSMO, the you could do a Burflags=D4 on the
PDC FSMO and do a burflags=D2 on all other DCs in the same AD domain
How to start?
Stop the NTFRS on all DCs in the domain. that will only disable replication
for NTFRS not the access to the SYSVOL
then start with the PDC FSMO in doing burflags=D4
then do each other DC one by one in doing Burflags=D2 (this will remove the
contents of the SYSVOL to a side-folder and therefore it is unavailable
until it inbound replicates from another DC) --> for the order of DCs, use
the nearest DC to the PDC FSMOs, nearest to the previous DC, next nearest AD
site, etc.

also see:
http://support.microsoft.com/kb/290762
http://support.microsoft.com/kb/315457

be carefull with this!

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Identity & Access - Directory Services #

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test ANY suggestion in a test environment before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Bob" <Bob@bobsyouruncle.com> wrote in message
news:uT8W$Wq8IHA.2348@TK2MSFTNGP06.phx.gbl...
> Hi Everyone.
>
> While trying to find out the reason that our remote sites aren't picking
> up the changes in group policies, I noticed that at our head office the
> NTFRS service was set to disabled.
>
> From the event logs, it has been stopped for 2 months. Which explains why
> no changes have reached the other sites.
>
> When I started the NTFRS service, there was the expected Event ID 13568.
>
> To get this server back into the replication set, I need to "Enable
> Journal Wrap Automatic Restore" in the registry.
>
> Problem is, this server has a whole lot of changes to group policies I
> have done over the last week. Will I lose those changes? Is there a way to
> do this without losing those changes?
>
>
>
> -------------------
>
>
> Event Type: Error
> Event Source: NtFrs
> Event Category: None
> Event ID: 13568
> Date: 31/07/2008
> Time: 10:19:56 AM
> User: N/A
> Computer: WALLTECH-SBS
> 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.
>