set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

J

Jenny

Hi guys,
Ive been getting this error alot of later and looked at a
few knowledge base articles but it still seems to be
occuring would someone please be able to help me???

thx

Jenny

:)
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:".

Following recovery steps will 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.
[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.
 
D

diasmith [MSFT]

Hello,

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.


Thank You.

Diana.

(e-mail address removed)

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

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

JRNL_WRAP_ERROR on SYSVOL 2
JRNL_WRAP_ERROR in FRS event log 4
SYSVOL Problem 1
AD GPO Replication 1
Journal Wrap Error 13568 in DC 4
NTFRS 5
Recovered Win2k BDC Replication error 3
fix Journal wrap error 4

Top