Journal_Wrap Errors

Here is an article that will explain what a journal wrap is:

292438 Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets

http://support.microsoft.com/?id=292438

The main thing here is to find out why this machine wound up in journal

wrap state.

To fix the journal wrap, you may have to perform a D2 (non authoratative
restore):

1. Click "Start", and then click "Run".

2. In the "Open" box, type "cmd" (without the quotation marks) and then
press ENTER.

3. In the "Command" box, type "net stop ntfrs" (without the quotation
marks).

4. Click "Start", and then click "Run".

5. In the "Open" box, type "regedit" (without the quotation marks) and then
press ENTER.

6. Locate the following subkey in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup
/Restore\Process at Startup

7. In the right pane, double-click "BurFlags".

8. In the "Edit DWORD Value" dialog box, type "D2" (without the quotation
marks) and then click "OK".

9. Quit Registry Editor, and then switch to the "Command" box.

10. In the "Command" box, type "net start ntfrs" (without the quotation
marks).

11. Quit the "Command" box.

When the FRS service restarts, the following actions occur:
- The value for BurFlags registry key returns to 0.
- Files in the reinitialized FRS folders are moved to a <Pre-existing>
folder.
- The FRS database is rebuilt.

- The member performs an initial join of the replica set from an upstream
partner or from the computer that is specified in the Replica Set Parent
registry key if a parent has been specified for SYSVOL replica sets.

- The reinitialized computer performs a full replication of the affected
replica sets when the relevant replication schedule begins.

thanks to Diana

from this URL: http://www.pcreview.co.uk/forums/set-domain-system-volume-sysvol-share-jrnl_wrap_error-t1448004.html