Avatar of jamescarson69
jamescarson69
Flag for United Kingdom of Great Britain and Northern Ireland asked on

Journal Wrap Error - SBS 2003 - Only DC in domain

Hi guys

I have an SBS 2003 SP2 server in a domain as the only DC.

I am getting the journal wraps error event ID 13568

Event Type:      Error
Event Source:      NtFrs
Event Category:      None
Event ID:      13568
Date:            11/02/2010
Time:            14:00:40
User:            N/A
Computer:      MIMRAM
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


When I follow the fix within the error and then run FRSdiag.exe tool I then get this error

SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Enable Journal Wrap Automatic Restore = 0 :: ERROR: Enabling Journal Wrap Automatic Restore is NOT recommended in post-SP2 version of FRS. Please see KB.292438 (Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets) for further information!


Is this still a Burflags fix? I'm a little at a loose end here and need some advice

Thanks in advanve
Active DirectoryWindows Server 2003

Avatar of undefined
Last Comment
jamescarson69

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
snusgubben

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
jamescarson69

ASKER
Thanks. The D2 non-authoritative seems to have done the trick
SOLUTION
ARK-DS

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
snusgubben

The author asked for an advice regarding JournalWrap and Burflags. He got the correct advice "from the book" that would have fixed his problem.

Ark-DS followed this up, so it should be a split and not a close.
snusgubben

The author asked for an advice regarding JournalWrap and Burflags. He got the correct advice "from the book" that would have fixed his problem.

Ark-DS followed this up, so it should be a split and not a close.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
snusgubben

The author asked for an advice regarding JournalWrap and Burflags. He got the correct advice "from the book" that would have fixed his problem.

Ark-DS followed this up, so it should be a split and not a close.
snusgubben

Tripple object :)
jamescarson69

ASKER
Wow! Taking on board the advice of Ark-DS and the triple objection of snusgubben and finally being told off by the moderator I have gone back to the drawing board.

I hold my hands up, it looks like being a D4. The pre-existing file is in the sysvol

I am working on this server remotely. What are the risks of the D4? I have used before but when all else had failed. Obviously I will backup the system state before attempting.

Humble apologies all


⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
snusgubben

The d2 flag will dump the current content of SYSVOL to the Pre_Existing folder and try to get new content from an inbound partner (the DC with the D4 flag).

Here is an excelent blog entry about the JournalWrap with all the links you'll need:

http://blogs.technet.com/instan/archive/2009/07/14/what-happens-in-a-journal-wrap.aspx
ARK-DS

Hi,

There is no risk in doing a D4 when you have only one DC. See, D4 means that you are making that DC authoritative to give the contents of its DFS share (sysvol here) to the other replica members (DCs/member servers hosting that DFS share : which are not present in our case). Hence there is no risk in doing a D4 in our case.

Regards,

Arun.
snusgubben

Both http:#a26613071 and http:#26615152 is correct and it should be a split
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
jamescarson69

ASKER
Points split. Thanks for the help guys.

Much appreciated.