No record of File Replication System, SYSVOL started

[Terje Trane]

I'm getting this error while running dcdiag:

Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.

This is the only Windows-server in the company, it exists here because we
needed an Exchange Mailserver, and had a Small Business license. (File and
print server is a Novell.) All users and PCs and are members of the domain,
so the log in to both novell and the windows domain simultaniously using the
netware login dialog.

Since this is a domain controller not replicating with anybody, and not
having anyone to replicate with, how do I get rid of the error? (do I need
to care about it?) It stared after the FRS service had been down for a long
time.

 

[Ray Lava [MSFT]]

Terje,

The message that you are seeing indicates that you may not have sysvol or
netlogon shared out on your domain controller. If this is the case, your
domain controller will not function properly.

Please go to a command prompt and type "net share". This will list all the
shares on that DC. Make sure that you have a sysvol and a netlogon share.
If you do not, try stopping and restarting your file replication service on
the Windows 2000 domain controller. If that does not work, you probably
have a DNS configuration problem. If the DC is running DNS, make sure that
it points to itself for DNS and that "allow dynamic updates" is set to yes
in your DNS manager.

If none of these things resolves the problem, please provide me with more
information including event log errors that you are getting. Thanks.


Ray Lava
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights

 

[Terje Trane]

The message that you are seeing indicates that you may not have sysvol or
netlogon shared out on your domain controller. If this is the case, your
domain controller will not function properly.

I'm not at the site at the moment so I can't check, but I believe they are
shared.

If that does not work, you probably
have a DNS configuration problem. If the DC is running DNS, make sure that
it points to itself for DNS and that "allow dynamic updates" is set to yes
in your DNS manager.

That might be worth checking. This is two W2k Advanced servers clustered in
an active/inactive pair. One is 10.0.0.1 and the other is 10.0.0.2. It is
set up as a virtual fileserver 10.0.0.3, (has an external disc cabinet
shared between the two servers) and provides DHCP-service. How should DNS be
set up for such a cluster? Will the PCs use 10.0.0.3 as DNS-adress? Do you
have a pointer to some clear documentation, checklists etc?

 

[Terje Trane]

Sorry forget about this entry, I mixed up two projects I'm working at at the
same time. I will post another corrected entry.

 

[Terje Trane]

Terje,

The message that you are seeing indicates that you may not have sysvol or
netlogon shared out on your domain controller. If this is the case, your
domain controller will not function properly.

SYSVOL and NETLOGON are there

If that does not work, you probably
have a DNS configuration problem. If the DC is running DNS, make sure that
it points to itself for DNS and that "allow dynamic updates" is set to yes
in your DNS manager.

This is ok

If none of these things resolves the problem, please provide me with more
information including event log errors that you are getting. Thanks.


Ray Lava
Microsoft Corporation

I get a lot of strange error messages, but it seems to start with

NtFrs Event ID 13568
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)"
:

The fix suggested in the error message (using "Enable Journal Wrap Automatic
Restore" )
doesn't seem to help.

It has probably started with the FRS service beeing down for a long time.

How do I fix this?