Home | Site Map | How To | Windows Vista | Case Studies | Articles | Forums | Services | Donations | Careers | About Us | Contact Us|

Web ChicagoTech
 

 

Perform a non-authoritative restore of the data

If FRS is experiencing journal wrap errors on a DC, it cannot replicate files until the condition has been cleared. To fix journal wrap errors, you should perform a Non-Authoritative Restore based on the OS and SP.

1. If the computer is running either the Windows 2000 (2195 binary), Windows 2000 SP1, or SP1 Hotfix (WINSE build 5298) versions of the Ntfrs.exe file, the non-authoritative restore process must be invoked manually by setting BURFLAGS=D2 in the Windows NT registry.

2. If the computer is using Windows 2000 SP2, or the Windows 2000 SP2 hotfix (WINSE 11773), versions of the Ntfrs.exe file, the service performs a programmatic non-authoritative restore when the journal_wrap_error is detected.

3. By default, Windows 2000 SP3 or above and Windows 2000 SP3 hotfix versions of the Ntfrs.exe file do not perform an automatic non-authoritative restore when journal wrap errors are detected. You may set the Enable journal wrap automatic restore registry key is set to 1 following these steps:

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
4. On the Edit menu, click Add Value, and then add the following registry value:
   Value name: Enable Journal Wrap Automatic Restore
   Data type: REG_DWORD
   Radix: Hexadecimal
   Value data: 1 (Default 0)
5. Quit Registry Editor.
6. Restart FRS.

Related Topics

Causes of Active Directory replication issues

FRS Tools

Perform a non-authoritative restore of the data

How to Repadmin.exe Tool to diagnose Replication Status

Troubleshooting File Replication Service Issues

Event ID 13568 - The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Event ID 1058 - Windows cannot access the file gpt.ini for GPO

Logon scripts don’t synchronize between two domain controllers

Group Policies may not update between DCs

“INFO: The policy object does not exist”

“RSoP data invalid. Likely causes are, data is corrupt, data has been deleted or data has never been created."

 

 

 

 

  This web is provided "AS IS" with no warranties.
Copyright © 2002-2007 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.