troubleshooting Question

Windows 2003 Domain Controller Error

Avatar of minniejp
minniejpFlag for United Kingdom of Great Britain and Northern Ireland asked on
Windows Server 2003Windows Server 2008
17 Comments1 Solution357 ViewsLast Modified:
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
ASKER CERTIFIED SOLUTION
minniejp

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 17 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 17 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros