• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 622
  • Last Modified:

journal wrap error in sbs 2008

I have a sbs2008 server that keeps giving event ID 13568 every time I reboot. I tried to push a group policy recently, but was unsuccessful, it was a software installer. I looked up several articles regarding this and I am getting conflicting messages. One is telling me to do this:
Click down the key path:
Double click on the value name
   “Enable Journal Wrap Automatic Restore”
and update the value. - See more at: http://blog.ronnypot.nl/?p=738#sthash.GJpYe9rU.dpuf

But then I read an article where that will cause issues with not being able to login because the sysvol disappears,


then I read an article that suggested I do a non-authoritive restore (D2) which would be the correct method...
But that confuses me as well. How can you do a non authoritative restore with no other DC on the network??
1. Click Start, and then click Run.
2. In the Open box, type cmd and then press ENTER.
3. In the Command box, type net stop ntfrs.

(make a backup copy of the contents of the Pre-existing folder if it exists, then copy those to the parent folder)
4. Click Start, and then click Run.
5. In the Open box, type regedit and then press ENTER.
6. Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\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 and then click OK.
9. Quit Registry Editor, and then switch to the Command box.
10. In the Command box, type net start ntfrs.
11. Quit the Command box.

Within a minute or two, you should see event ID 13516 post in the event viewer:
see the link below...
Another post says to do a D4
1 Solution
Neeraj KumarCommented:
williamstechnologygroupAuthor Commented:
Thank you, I think that did the trick. I have been doing this for a long time, but I always get nervous messing with AD and the Sysvol. I did run the best practice analyzer and it did not show the error. I am assuming it will not show up in the event viewer on the next reboot as well.....

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now