Ntfrs problem

My present environmen Windows 2000 SP4 single DC ; 15 clients PC

I need to install a Windows 2008 R2 and promote it as a DC

In the event log NTFRS of the 2000 server, each time the server is rebooted I receive 2 messages
1) replication service is starting ID 13501
2) "DOMAIN SYSTEM VOLUME (SYSVOL SHARE) is in JRNL_WRAP_ERROR ID 13568 asking me to modify registry "enable journal wrap automatic restore" and other options

I DO NOT receive the Ntfrs message telling me that this server is OK as a DC ( and talking about SYSVOL Share (ID 13516)

THis problem has been existing since 2006 (date appears in the NTFRS event log) without giving any problem. The server is wokging well. Sysvol and Netlogon are actually shared and clients opening session without problem


1) Would I be able to promote a 2008 R2 server to a DC with this NTFRS error ? (this 2000 server will go offline after promotion of the 2008 DC)
2) If not what is the solution to this problem ?

  Thank you
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.

Krzysztof PytkoSenior Active Directory EngineerCommented:
Follow with this article from eventid.net
and SYSVOL errors should disppear

for JRNL_WRAP_ERROR ID 13568 error, check how to fix FRS issues from MS at

after that make sure that your Domain Functional Level is set to Windows 2000 native mode. 2008 doesn't work with NT4 domain and 2000 mixed moed DFL is not supported.

How to add firts 2008R2 DC into 2000 network you can find on my blog at


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
gadsadAuthor Commented:
If I do NOT solve this problem and I leave it as it is now would I be able to promote a new Windows 2008 DC ?

Or do i MUST solve the problem before ?

Thank you
Krzysztof PytkoSenior Active Directory EngineerCommented:
Each time you want to add new DC, you must be sure that there is no problem with any AD related part to prevent any issues. When you prepare an environment for new 2008 R2 DC it might work fine, but it might not work. This can lead to AD replication issue with SYSVOL and NETLOGON (GPOs and logon scripts) but if you wish, start installing new DC and you will check. You can always demote that new DC before it will be productive and solve issues. In case of SYSVOL and NETLOGON issues you can try to rebuild them as it's described in this MS article at

but for start, run on your 2000DC in command-line netdiag to check domain/forest condition

gadsadAuthor Commented:
I did what you say and the problem was solved

Thank you very much
Krzysztof PytkoSenior Active Directory EngineerCommented:
Great! You're welcome :)

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 2000

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.