JRNL_WRAP_ERROR

  • Thread starter Thread starter Dunc
  • Start date Start date
D

Dunc

Hi,

I've got an AD network with three DC's. The first DC started getting a
few FRS errors after Service Pack4. I found out that was because SP4
tries to increase the journal size and we didn't have enough disk
space. I've now corrected this, got rid of the two error messages but
am now getting a message saying the DOMAIN SYSTEM VOLUME (SYSVOL
SHARE) is in JRNL_WRAP_ERROR. Have looked at the FRS troubleshooting
at Microsoft, but the registry changes it suggests are not meant to be
done post SP3. How can I resolve this problem? Do I need to do a
non-authorative restore? Can I do this on the first DC? (domain naming
master, schema master and all that) or do I need to transfer the roles
first?

Any advise appreciated!
Thanks
 
If the other source DC's are online and functioning then you will only need
to set burflags D2 on the DC presenting itself with the journal wrap. If we
are certain that the problem was the increased journal size and low disk
space then the non-auth restore will be fine.

Other items that cause journal wraps include older antivirus programs
scanning sysvol, backup programs, and setting security on sysvol contents
through policy. These items in the latest service pack will only show a
suppression event in the NTFRS logs and will not replicate the changes out
potentially causing a replication storm.

Hope that helps

Steve Dodson [MSFT]
Directory Services


--------------------
From: (e-mail address removed) (Dunc)
Newsgroups: microsoft.public.win2000.active_directory
Subject: JRNL_WRAP_ERROR
Date: 22 Oct 2003 05:02:00 -0700
Organization: http://groups.google.com
Lines: 16
Message-ID: <[email protected]>
NNTP-Posting-Host: 81.136.235.66
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1066824121 3048 127.0.0.1 (22 Oct 2003 12:02:01 GMT)
X-Complaints-To: (e-mail address removed)
NNTP-Posting-Date: Wed, 22 Oct 2003 12:02:01 +0000 (UTC)
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onlin
e.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!postnews1.google.com!no
t-for-mail
Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.active_directory:52801
X-Tomcat-NG: microsoft.public.win2000.active_directory

Hi,

I've got an AD network with three DC's. The first DC started getting a
few FRS errors after Service Pack4. I found out that was because SP4
tries to increase the journal size and we didn't have enough disk
space. I've now corrected this, got rid of the two error messages but
am now getting a message saying the DOMAIN SYSTEM VOLUME (SYSVOL
SHARE) is in JRNL_WRAP_ERROR. Have looked at the FRS troubleshooting
at Microsoft, but the registry changes it suggests are not meant to be
done post SP3. How can I resolve this problem? Do I need to do a
non-authorative restore? Can I do this on the first DC? (domain naming
master, schema master and all that) or do I need to transfer the roles
first?

Any advise appreciated!
Thanks
Click to expand...


--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Back
Top