Guest Chema Posted October 2, 2007 Posted October 2, 2007 Hi, somebody i've a problem, i have 2 DC, the principal has the DNS, is the second time that freezed, i was cheking the event viewer and the first error is in the File replication services,; i don't know do, this is the message: please i need help.. Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13568 Date: 10/1/2007 Time: 7:02:41 PM User: N/A Computer: SERVER-DC-01 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:\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:". 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
Guest Meinolf Weber Posted October 2, 2007 Posted October 2, 2007 Re: Journal Wrap Error 13568 in DC Hello Chema, Did you check the registry like mentioned in the event description? http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Hi, somebody > > i've a problem, i have 2 DC, the principal has the DNS, is the second > time that freezed, i was cheking the event viewer and the first error > is in the File replication services,; i don't know do, this is the > message: > > please i need help.. > > Event Type: Error > Event Source: NtFrs > Event Category: None > Event ID: 13568 > Date: 10/1/2007 > Time: 7:02:41 PM > User: N/A > Computer: SERVER-DC-01 > 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:\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:". > 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 >
Guest Chema Posted October 2, 2007 Posted October 2, 2007 Re: Journal Wrap Error 13568 in DC Hi Meinolf., tnks for help me., but in this case this solutions talking about Windows 2000 SP2, my OS is W2k SP4 and i didn't find a articule that talking about it's.. if you know more over this topic i'll tnks very much. Best regards Chema "Meinolf Weber" wrote: > Hello Chema, > > Did you check the registry like mentioned in the event description? > > http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1 > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > Hi, somebody > > > > i've a problem, i have 2 DC, the principal has the DNS, is the second > > time that freezed, i was cheking the event viewer and the first error > > is in the File replication services,; i don't know do, this is the > > message: > > > > please i need help.. > > > > Event Type: Error > > Event Source: NtFrs > > Event Category: None > > Event ID: 13568 > > Date: 10/1/2007 > > Time: 7:02:41 PM > > User: N/A > > Computer: SERVER-DC-01 > > 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:\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:". > > 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 > > > > >
Guest Meinolf Weber Posted October 3, 2007 Posted October 3, 2007 Re: Journal Wrap Error 13568 in DC Hello Chema, Even if the SP is higher, just looking doesn't harm the system.:-) Also did you check the provided solution from the event viewer entry? Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Hi Meinolf., > > tnks for help me., > but in this case this solutions talking about Windows 2000 SP2, my OS > is W2k > SP4 and i didn't find a articule that talking about it's.. > if you know more over this topic i'll tnks very much. > > Best regards > Chema > "Meinolf Weber" wrote: > >> Hello Chema, >> >> Did you check the registry like mentioned in the event description? >> >> http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source= >> NtFrs&phase=1 >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> Hi, somebody >>> >>> i've a problem, i have 2 DC, the principal has the DNS, is the >>> second time that freezed, i was cheking the event viewer and the >>> first error is in the File replication services,; i don't know do, >>> this is the message: >>> >>> please i need help.. >>> >>> Event Type: Error >>> Event Source: NtFrs >>> Event Category: None >>> Event ID: 13568 >>> Date: 10/1/2007 >>> Time: 7:02:41 PM >>> User: N/A >>> Computer: SERVER-DC-01 >>> 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:\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:". >>> 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
Guest Chema Posted October 19, 2007 Posted October 19, 2007 Re: Journal Wrap Error 13568 in DC Hello Meinolf., pleas help me., The last week implemente the solucion that you sent me but didn't work, the error happed each week, for example., the last error was on 11 Octuber and just to yestarday happened again, each 8 days happend the error, the most crtical is taht my server freezen, the principal Domain controller and the second DC too,. i've to shut down, y restart., i did check the logs and the frist error is : i've been found ohter solution but i didn't find nothing., please if you have other idea please tell me., tnks so much, Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13568 Date: 10/18/2007 Time: 6:51:51 PM User: N/A Computer: FTAA-DC-01 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:\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:". 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. "Meinolf Weber" wrote: > Hello Chema, > > Even if the SP is higher, just looking doesn't harm the system.:-) Also did > you check the provided solution from the event viewer entry? > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > Hi Meinolf., > > > > tnks for help me., > > but in this case this solutions talking about Windows 2000 SP2, my OS > > is W2k > > SP4 and i didn't find a articule that talking about it's.. > > if you know more over this topic i'll tnks very much. > > > > Best regards > > Chema > > "Meinolf Weber" wrote: > > > >> Hello Chema, > >> > >> Did you check the registry like mentioned in the event description? > >> > >> http://www.eventid.net/display.asp?eventid=13568&eventno=1743&source= > >> NtFrs&phase=1 > >> > >> Best regards > >> > >> Meinolf Weber > >> Disclaimer: This posting is provided "AS IS" with no warranties, and > >> confers > >> no rights. > >>> Hi, somebody > >>> > >>> i've a problem, i have 2 DC, the principal has the DNS, is the > >>> second time that freezed, i was cheking the event viewer and the > >>> first error is in the File replication services,; i don't know do, > >>> this is the message: > >>> > >>> please i need help.. > >>> > >>> Event Type: Error > >>> Event Source: NtFrs > >>> Event Category: None > >>> Event ID: 13568 > >>> Date: 10/1/2007 > >>> Time: 7:02:41 PM > >>> User: N/A > >>> Computer: SERVER-DC-01 > >>> 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:\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:". > >>> 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 > > >
Guest Meinolf Weber Posted October 19, 2007 Posted October 19, 2007 Re: Journal Wrap Error 13568 in DC Hello Chema, Check also this: http://support.microsoft.com/kb/292438/en-us http://technet.microsoft.com/en-us/library/Bb727056.aspx#EFAA Run also dcdiag and netdiag and post the result here from both DC's. And please an unedited ipconfig /all from both servers. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Hello Meinolf., > > pleas help me., > > The last week implemente the solucion that you sent me but didn't > work, the error happed each week, for example., the last error was on > 11 Octuber and just to yestarday happened again, each 8 days happend > the error, the most crtical is taht my server freezen, the principal > Domain controller and the second DC too,. > > i've to shut down, y restart., i did check the logs and the frist > error is : i've been found ohter solution but i didn't find nothing., > please if you have other idea please tell me., > > tnks so much, > > Event Type: Error > Event Source: NtFrs > Event Category: None > Event ID: 13568 > Date: 10/18/2007 > Time: 6:51:51 PM > User: N/A > Computer: FTAA-DC-01 > 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:\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:". > 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. > > "Meinolf Weber" wrote: > >> Hello Chema, >> >> Even if the SP is higher, just looking doesn't harm the system.:-) >> Also did you check the provided solution from the event viewer entry? >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> Hi Meinolf., >>> >>> tnks for help me., >>> but in this case this solutions talking about Windows 2000 SP2, my >>> OS >>> is W2k >>> SP4 and i didn't find a articule that talking about it's.. >>> if you know more over this topic i'll tnks very much. >>> Best regards >>> Chema >>> "Meinolf Weber" wrote: >>>> Hello Chema, >>>> >>>> Did you check the registry like mentioned in the event description? >>>> >>>> http://www.eventid.net/display.asp?eventid=13568&eventno=1743&sourc >>>> e= NtFrs&phase=1 >>>> >>>> Best regards >>>> >>>> Meinolf Weber >>>> Disclaimer: This posting is provided "AS IS" with no warranties, >>>> and >>>> confers >>>> no rights. >>>>> Hi, somebody >>>>> >>>>> i've a problem, i have 2 DC, the principal has the DNS, is the >>>>> second time that freezed, i was cheking the event viewer and the >>>>> first error is in the File replication services,; i don't know do, >>>>> this is the message: >>>>> >>>>> please i need help.. >>>>> >>>>> Event Type: Error >>>>> Event Source: NtFrs >>>>> Event Category: None >>>>> Event ID: 13568 >>>>> Date: 10/1/2007 >>>>> Time: 7:02:41 PM >>>>> User: N/A >>>>> Computer: SERVER-DC-01 >>>>> 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:\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:". >>>>> 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
Recommended Posts