Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Windows 2003 Domain Controller Error

Posted on 2014-01-03
17
324 Views
Last Modified: 2014-01-25
Experts,

I have a Windows 2003 Domain Controller and have recently installed a Windows 2008 Server as its replacement.  Once I added the DC role to the 2008 Server, I noticed the 2008 box did not have the sysvol or netlogon share.  Upon further investigation, I found this error in the event viewer on the 2003 server:  This is a small site with around 15 users, connected via vpn to their head office.  So there are two domains, domain1 which is giving the error below and domain2 which is fine.  I have done some reading on the error and as this site is so small, it didn't need a second machine hence why there was only one DC.  I don't have another domain to pull the data from, which is worrying me somewhat.  The new DC, i'm going to assume would be of no use, giving the fact it is not replicating from the current DC (2003 Server).

"The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
 
 Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 Replica root path is   : "c:\windows\sysvol\domain"
 Replica root volume is : "\\.\C:"
 A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.
 
 [1] Volume "\\.\C:" has been formatted.
 [2] The NTFS USN journal on volume "\\.\C:" has been deleted.
 [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
 [4] File Replication Service was not running on this computer for a long time.
 [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
 Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
 [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
 [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
 
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.


Cheers
0
Comment
Question by:minniejp
  • 8
  • 5
  • 3
  • +1
17 Comments
 
LVL 17

Expert Comment

by:WORKS2011
ID: 39755429
Have you demoted the SBS2003 yet?
0
 

Author Comment

by:minniejp
ID: 39755431
not yet no
0
 
LVL 17

Expert Comment

by:WORKS2011
ID: 39755435
you know you can't have two DC's in a domain, right? Sorry not talking down to you I'm trying to get my notes together for migrating. It appears they haven't handed off to one another, this appears to be the case. Did you use an answer file or build the 2008 server by hand.
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

Author Comment

by:minniejp
ID: 39755437
Why can't you have two DC's in a domain?
0
 
LVL 17

Expert Comment

by:WORKS2011
ID: 39755441
sorry, I meant PDC's and may have got ahead of myself.
0
 

Author Comment

by:minniejp
ID: 39755442
The first server has all the roles and is still the pdc.  As I cannot see the sysvol etc, I am not able to transfer the roles, hence why I went looking to see what was wrong.
0
 
LVL 17

Expert Comment

by:WORKS2011
ID: 39755444
I'm pulling from memory, was ADPREP run correctly?

It wouldn't hurt to run dcdaig /test:dns on the 2008 server, it may give an indication what's going on.
0
 

Author Comment

by:minniejp
ID: 39755449
the problem is with the original server, not the new one.  Its not replicating to the new dc
0
 
LVL 17

Expert Comment

by:WORKS2011
ID: 39755454
I'm pretty sure DNS has to be working correctly for it to work but I may be off on this.

What mode are you running the 2003 server in?
0
 
LVL 34

Expert Comment

by:Seth Simmons
ID: 39755516
have you seen this article?

How to troubleshoot journal_wrap errors on Sysvol and DFS replica sets

http://support.microsoft.com/kb/292438
0
 

Author Comment

by:minniejp
ID: 39755794
Server is running in Window 2003.  I'm confused, active directory is replicating just fine, but the Netlogon and sysvol shares are not appearing on the new dc
0
 

Expert Comment

by:Ithizar
ID: 39756855
In the original question, you did not mention SBS2003 (Windows Small Business Server 2003), but the first reply mentioned it. Just to clarify... are you discussing regular Windows Server 2003 or SBS2003. Because if it's the latter, I believe it's true that you can only have one domain controller per domain. If it's the former, you should be able to have multiple DC's.
0
 
LVL 34

Expert Comment

by:Seth Simmons
ID: 39756928
SBS does allow for multiple domain controllers.  The rules are that the SBS server must be at the root of the forest and hold the FSMO roles.  No trust relationships or other SBS servers can exist.

http://blogs.technet.com/b/sbs/archive/2007/10/04/debunking-the-myth-about-additional-domain-controllers-replica-dcs-in-an-sbs-domain.aspx
0
 

Author Comment

by:minniejp
ID: 39757221
It is standard.
0
 
LVL 34

Expert Comment

by:Seth Simmons
ID: 39757330
how did you determine that replication is working fine?
have you tried to demote the 2008 server and promote again?
0
 

Accepted Solution

by:
minniejp earned 0 total points
ID: 39793799
I performed an authoritative restore and this worked.
0
 

Author Closing Comment

by:minniejp
ID: 39808389
This problem was resolved by performing an authoritative restore.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
OfficeMate Freezes on login or does not load after login credentials are input.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

789 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question