Windows Server 2003 SP2 with a replication error (this is the only DC in the domain) [image below]: Journal Wrap Error on sysvol share

  • Is there a way to find out what is broken/corrupt/malformed in this DC's sysvol?
  • Is there a way to fix the sysvol share other than from a system-state restore point (which we don't have), or from another domain controller (which we also don't have)?

alt text

1 Answer 1


There isn't any "corruption". Rather, too many changes happened in the NTFS volume that hosts the SYSVOL in a short period of time, overflowing the NTFS change journal. Rather than explain it in detail, I'll direct you to some background on what causes journal wrap errors in this blog posting.

The two recovery methods are described in this Microsoft KB article.

Since you have no replication partners you should be fine performing an authoritative restore (as described in that KB article). In multi-DC scenarios this is not the preferred method.

Basically, you'll stop the File Replication Service (FRS), set the "burflags" registry value to "D4" (the full path is in the article), and restart the FRS. That should get you back up and running.

Before you try any of that, though, I'd at least make a current System State backup to disk.

You might want to think about getting a second DC after all of this is said and done. It's cheap insurance, makes disaster recovery a LOT easier, and in this scenario would've preserved client access to Group Policy during the outage.

  • Spot on Evan!... I had half-read that MS KB, and didn't seem clear that it would rebuild the journal. Everything is peachy now, thanks! (btw, we found this issue as we were bringing a new DC in)
    – l0c0b0x
    Dec 15, 2010 at 1:07

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .