dcdiag error the sysvol can prevent the AD from starting

  • Thread starter Thread starter Cedric
  • Start date Start date
C

Cedric

I'm receiving the following error when running DCDIAG on
my windows 2000 server Domain Controller

Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.

How do I fix this error??
 
Hi,

I used regedit and follow your instuctions to:

HKey_Local_Machine/System/CurrentControlSet/Services/NtFrs/
Parameters/SysVol seeding

their is no entry for:

Domain System Volume (SYSVOL share)

How can I fix these settings??


there

Seeding/
-----Original Message-----
Hi,

1. Determine which domain controller the server is sourcing Sysvol from:

HKey_Local_Machine/System/CurrentControlSet/Services/NtFrs /Parameters/SysVol

Seeding/ Domain System Volume (SYSVOL share)

Replica Set Parent =\\SourceDC.Domain.com

You may need to stop NTFRS, delete the double backslashes in the Replica
Set Parent
value and then restart NTFRS

250545 SYSVOL Directory Is Slow to Synchronize, Delays Creation of SYSVOL
Share
<http://support.microsoft.com/?id=250545>


2. Verify health of Sysvol content on the source domain controller
-Is it shared? If not shared, is the source domain controller in a D2
state due to
a Journal Wrap or other problem?

292438 Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets
<http://support.microsoft.com/?id=292438>

What does the folder structure look like?
-Check for the existence of the
Click to expand...
NtFrs_PreExisting___See_EventLog in
%SystemRoot%\Sysvol\Sysvol\Domain.Com directory
This would most likely indicate that it is sourcing Sysvol content from its
upstream partner. (D2)

3. Verify Staging Area isn't full:
264822 File Replication Service Stops Responding When Staging Area is Full
<http://support.microsoft.com/?id=264822>

307777 Possible Causes of a Full File Replication Service Staging Area
<http://support.microsoft.com/?id=307777>

4. Verify Active Directory Replication is successful between the two domain
controllers through AD Sites and Services and by running REPADMIN /SHOWREPS
on both
servers

5. Verify that you are able to ping the DNS alias of each DC involved
Ping <DsaGuid>._msdcs.<ForestDnsName>
¤DSA Guid can be determined by looking in
Click to expand...
REPADMIN /SHOWREPS or Looking in
 
Back
Top