[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2331
  • Last Modified:

Missing contents of sysvol and netlogon folder

After installing a Windows Server 2003 domain controller in my domain the sysvol \ netlogon folder is empty and not shared.  The folders are available on the first domain controller a Windows Server 2000 machine. What do I do?
0
CurtisKing
Asked:
CurtisKing
  • 5
  • 3
  • 2
3 Solutions
 
PlaceboC6Commented:
How long has it been since you promoted the new DC?

Ensure that the new DC is pointing to the old DC for DNS only.
Check the old DC's File Replication Service event log and make sure there aren't any errors.

This may help as well:

http://support.microsoft.com/kb/257338/en-us
0
 
cedarghostCommented:
Sounds like a problem with the file replication service and sysvol is not getting replicated. Try  backing up the sysvol data on the machine that has it  Look for a file called  ntfrs.jdb.Stop FRS and then rename that file. Then restart FRS. let me know if this helps.
0
 
cedarghostCommented:
You may also want to check this out. It is an article from Microsoft on step-by-step troubleshooting for missing sysvol and netlogon folders:
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=7394
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
CurtisKingAuthor Commented:
The new DC was promoted last week Wednesday.
0
 
PlaceboC6Commented:
K.  So we don't have to worry about a broken channel or tombstoning at least.

I would verify the DNS configuration of the new DC.

Check the directory services log as well and see if there is a problem with database replication and the KCC building replication connects.  If this doesn't happen,  then sysvol and netlogon won't replicate successfully.
0
 
CurtisKingAuthor Commented:
NTDS KCC ERROR 1925
The attempt to establish a replication link for the following writable directory partition failed.
 
Directory partition:
CN=Configuration,DC=nsc,DC=org
Source domain controller:
CN=NTDS Settings,CN=MEDIA1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nsc,DC=org
Source domain controller address:
6b89213a-cf8f-420a-8cb9-eba916fd4997._msdcs.nsc.org
Intersite transport (if any):
 
 
This domain controller will be unable to replicate with the source domain controller until this problem is corrected.  
 
User Action
Verify if the source domain controller is accessible or network connectivity is available.
 
Additional Data
Error value:
8524 The DSA operation is unable to proceed because of a DNS lookup failure.


This is the error.

I can't backup the sysvol file  right now cedarghost since files are in use in that folder, namely scripts etc.
 
0
 
PlaceboC6Commented:
Open the _MSDCS folder in DNS and make sure you see two (or more) GUID's.  One for each domain controller.  

Like:

6b89213a-cf8f-420a-8cb9-eba916fd4997._msdcs.nsc.org
0
 
CurtisKingAuthor Commented:
yes I see one for each dc and folders dc,domains,pdc
0
 
CurtisKingAuthor Commented:
Got rid of the error message above.
When I look at the FRS log
There is a warning message event id 13508. It was reporting failed attempts to replicate the sysvol folder
0
 
CurtisKingAuthor Commented:
Viewing the frs logs on the pc I couldn't replicate from(WIN 2000 DC) event id 13658 was repeated. I followed the directions given in that log see below and the sysvol folder on the win 2k3 domain controller was successfully replicated.

Event Type:      Error
Event Source:      NtFrs
Event Category:      None
Event ID:      13568
Date:            2008-02-18
Time:            11:59:02 AM
User:            N/A
Computer:      TEST
Description:
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:\winnt\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.
 
To change this registry parameter, run regedit.
 
Click on Start, Run and type regedit.
 
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
   "System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
   "Enable Journal Wrap Automatic Restore"
and update the value.
 
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
 
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now