event id 13568 journal wrap

Will the fix for this damage anything? I have windows 2003 r2 domain controller getting this error message every couple of minutes.
lkuhnerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PlaceboC6Commented:
You have nothing to lose.  The local copy of sysvol is trashed.  If you have another DC that is running and sysvol is healthy,  doing the fix on the R2 box will cause it to get rid of its bad copy and immediately pull from a reliable source.

0
lkuhnerAuthor Commented:
What server sysvol is bad the one getting the journal wrap error? Should I do system state backups on both servers?
0
PlaceboC6Commented:
The server with journal wrap errors in the FRS log is the one that is bad.   There is a registry key in the error message that will fix the issue.  Assuming you have a good copy of sysvol running on the other DC.

Although doing the fix on the bad dc shouldn't hurt anything (it's already messed up),  I'm always a fan of good system state backups.  :)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

lkuhnerAuthor Commented:
People can still log in. So I assume the other domain controller is functioning normal. How can I tell?
0
lkuhnerAuthor Commented:
I am also getting 1030 and 1058 errors are they the same issue?
0
PlaceboC6Commented:
1030 and 1058 means that the client is trying to apply group policy and it is failing.  If these errors are on the server,  it is because it is looking locally to apply Group Policy and since you are in journal wrap and your sysvol is broken...it is failing.

Typically these errors can be because of dns configuration, network issue, someone turned off a DC for some reason, etc....however in this case we know the server itself is in journal wrap.
0
lkuhnerAuthor Commented:
We added a 3 dc in last week before we knew we had this issue. If the second server is good would it have replicated to the third as far as the sysvol is concerned?
0
lkuhnerAuthor Commented:
What if we transfer the fsmo roles over to the good server. Would that fix the issue?
0
PlaceboC6Commented:
No.  

A journal wrap condition is independent of anything such as FSMO roles and the AD database itself.  This is a file replication breakdown for group policy files only.
0
lkuhnerAuthor Commented:
ok. I just checked and the two other servers say scecli are being applied correctly. Is that a good sign?
0
PlaceboC6Commented:
Yes indeed that is a good sign.
0
lkuhnerAuthor Commented:
Thanks man. We are good to go.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.