File Replication Event 13568

I have an error I have been unable to resolve on SBS 2003. Implemented Feb.
2007
Errors started 7/2007. Abot 2 a day. Here is Log data

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 1/12/2008
Time: 10:54:13 PM
User: N/A
Computer: JCLSBS
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.

rbrandtii wrote:
> I have an error I have been unable to resolve on SBS 2003.
> Implemented Feb. 2007
> Errors started 7/2007. Abot 2 a day. Here is Log data
>
> Event Type: Error
> Event Source: NtFrs
> Event Category: None
> Event ID: 13568
> Date: 1/12/2008
> Time: 10:54:13 PM
> User: N/A
> Computer: JCLSBS
> 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.
>

Have you followed the instructions below yet?

> 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.

--
/kj

Hi,

Thanks for posting in our newsgroup.

From your description, I know that you received this Event error "NtFrs,
13568" on the SBS 2003 Server. If that's not right, please don't hesitate
to let me know.

I. Firstly, I would like to know how many Domain Controllers are there
exists in the SBS domain. If there are multiple DCs, let's do the following:

1. Stop FRS.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup
/Restore/Process at Startup
4. On the Edit menu, click Add Value, and then add the following registry
value:
Value name: BurFlags
Data type: REG_DWORD
Radix: Hexadecimal
Value data: D2
5. Quit Registry Editor.
6. Restart FRS.

II. If SBS Server is the only DC in the domain, please type D4 as the
data of BurFlags value, and restart the FRS service as following:

1. Stop FRS.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup
/Restore/Process at Startup
4. On the Edit menu, click Add Value, and then add the following registry
value:
Value name: BurFlags
Data type: REG_DWORD
Radix: Hexadecimal
Value data: D4
5. Quit Registry Editor.
6. Restart FRS.

If the problem persists, please help me collect the following information
for deep research:

MPS Report

a. Visit
http://download.microsoft.com/downlo...5-a579-30b0bd9
15706/MPSRPT_DirSvc.EXE to download the file.
b. Run the MPSRPT_DirSvc.exe on the server box.
c. Wait for 10~15 minutes.
d. Open Windows explorer, navigate to
%SYSTEMROOT%\MPSReports\DirSvc\Logs\cab\
e. Send the .cab file directly to v-robeli@microsoft.com with subject:
41359287-File Replication Event 13568.

I am looking forward to hear from you.

If you need further assistance, please don't hesitate to let me know.

Best regards,

Robert Li(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================

This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities...s/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

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

--------------------
<Thread-Topic: File Replication Event 13568
<thread-index: AchdYYT/wtLrreCNS/uDOPAjLIxNCQ==
<X-WBNR-Posting-Host: 207.46.192.207
<From: =?Utf-8?B?cmJyYW5kdGlp?= <rbrandtii@discussions.microsoft.com>
<Subject: File Replication Event 13568
<Date: Tue, 22 Jan 2008 17:44:40 -0800
<Lines: 64
<Message-ID: <D3696D23-FF67-43BC-8491-B841A4C6B676@microsoft.com>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
<Newsgroups: microsoft.public.windows.server.sbs
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:88068
<NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<I have an error I have been unable to resolve on SBS 2003. Implemented
Feb.
<2007
<Errors started 7/2007. Abot 2 a day. Here is Log data
<
<Event Type: Error
<Event Source: NtFrs
<Event Category: None
<Event ID: 13568
<Date: 1/12/2008
<Time: 10:54:13 PM
<User: N/A
<Computer: JCLSBS
<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.
<
<
<
<
<

And, also, I have seen JWrap errors when the Sys Vol is being scanned by
real time file level Anti Virus.

Not sure of the event id code, however.

In any case, if you have not, please add the sysvol to the list of
exclusions for your file level av scans.

--
Larry

<v-robeli@online.microsoft.com> wrote in message
news:OomjOamXIHA.7844@TK2MSFTNGHUB02.phx.gbl...
> Hi,
>
> Thanks for posting in our newsgroup.
>
> From your description, I know that you received this Event error "NtFrs,
> 13568" on the SBS 2003 Server. If that's not right, please don't hesitate
> to let me know.
>
> I. Firstly, I would like to know how many Domain Controllers are there
> exists in the SBS domain. If there are multiple DCs, let's do the
> following:
>
> 1. Stop FRS.
> 2. Start Registry Editor (Regedt32.exe).
> 3. Locate and click the following key in the registry:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup
> /Restore/Process at Startup
> 4. On the Edit menu, click Add Value, and then add the following registry
> value:
> Value name: BurFlags
> Data type: REG_DWORD
> Radix: Hexadecimal
> Value data: D2
> 5. Quit Registry Editor.
> 6. Restart FRS.
>
> II. If SBS Server is the only DC in the domain, please type D4 as the
> data of BurFlags value, and restart the FRS service as following:
>
> 1. Stop FRS.
> 2. Start Registry Editor (Regedt32.exe).
> 3. Locate and click the following key in the registry:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup
> /Restore/Process at Startup
> 4. On the Edit menu, click Add Value, and then add the following registry
> value:
> Value name: BurFlags
> Data type: REG_DWORD
> Radix: Hexadecimal
> Value data: D4
> 5. Quit Registry Editor.
> 6. Restart FRS.
>
> If the problem persists, please help me collect the following information
> for deep research:
>
> MPS Report
>
> a. Visit
> http://download.microsoft.com/downlo...5-a579-30b0bd9
> 15706/MPSRPT_DirSvc.EXE to download the file.
> b. Run the MPSRPT_DirSvc.exe on the server box.
> c. Wait for 10~15 minutes.
> d. Open Windows explorer, navigate to
> %SYSTEMROOT%\MPSReports\DirSvc\Logs\cab\
> e. Send the .cab file directly to v-robeli@microsoft.com with subject:
> 41359287-File Replication Event 13568.
>
> I am looking forward to hear from you.
>
> If you need further assistance, please don't hesitate to let me know.
>
> Best regards,
>
> Robert Li(MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities...s/default.aspx
>
> When opening a new thread via the web interface, we recommend you check
> the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In
> doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
>
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> --------------------
> <Thread-Topic: File Replication Event 13568
> <thread-index: AchdYYT/wtLrreCNS/uDOPAjLIxNCQ==
> <X-WBNR-Posting-Host: 207.46.192.207
> <From: =?Utf-8?B?cmJyYW5kdGlp?= <rbrandtii@discussions.microsoft.com>
> <Subject: File Replication Event 13568
> <Date: Tue, 22 Jan 2008 17:44:40 -0800
> <Lines: 64
> <Message-ID: <D3696D23-FF67-43BC-8491-B841A4C6B676@microsoft.com>
> <MIME-Version: 1.0
> <Content-Type: text/plain;
> < charset="Utf-8"
> <Content-Transfer-Encoding: 7bit
> <X-Newsreader: Microsoft CDO for Windows 2000
> <Content-Class: urn:content-classes:message
> <Importance: normal
> <Priority: normal
> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
> <Newsgroups: microsoft.public.windows.server.sbs
> <Path: TK2MSFTNGHUB02.phx.gbl
> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:88068
> <NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
> <X-Tomcat-NG: microsoft.public.windows.server.sbs
> <
> <I have an error I have been unable to resolve on SBS 2003. Implemented
> Feb.
> <2007
> <Errors started 7/2007. Abot 2 a day. Here is Log data
> <
> <Event Type: Error
> <Event Source: NtFrs
> <Event Category: None
> <Event ID: 13568
> <Date: 1/12/2008
> <Time: 10:54:13 PM
> <User: N/A
> <Computer: JCLSBS
> <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.
> <
> <
> <
> <
> <
>