Sysvol not replicating but no NTFRS errors

[Luca]

Got some problems with the sysvol directory not replicating between two
servers which are in the same site. Both are obviously DC's and they are
also GC's. Connectivity is fine, DNS is fine, Active Directory changes get
replicated immediately between the two DC's.

The strange thing is that im not getting any errors File Replication
Services event log. I was getting this error last week:

Event ID 13559
The File Replication Service has detected that the replica root path has
changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If
this is an intentional move then a file with the name
NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
This was detected for the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
.......

I did what the error suggested and created a file named
NTFRS_CMD_FILE_MOVE_ROOT under the root path which stopped the error
occurring and after that this event was logged on both DC's:

event id 13516:
The File Replication Service is no longer preventing the computer from
becoming a domain controller. The system volume has been successfully
initialized and the Netlogon service has been notified that the system volume
is now ready to be shared as SYSVOL.

But as yet no sysvol replication has taken place, could it be something to
do with the Journal being Wrapped? Do i need to do the BurFlags and D2
procedure?

any help would be great. thanks.

[Parijat]

Hi Luca,

If you have received Event ID 13516 in the FRS event logs, which confirms
that both Sysvol and Netlogon are shared and initialized. There should not be
any further issues with the contents of the sysvol folder not replicating.

Couple of things that you could further check -

1. NTFS and Share Permissions (ACLs) on the Sysvol tree structure.
2. If everything still looks fine, you can definitely do a non-authoritative
restore (D2)
on one of the DCs. But please make sure that all the other DCs are not
complaining about any issues related to FRS or AD replication.


Regards,

Parijat...


"Luca" wrote:

> Got some problems with the sysvol directory not replicating between two
> servers which are in the same site. Both are obviously DC's and they are
> also GC's. Connectivity is fine, DNS is fine, Active Directory changes get
> replicated immediately between the two DC's.
>
> The strange thing is that im not getting any errors File Replication
> Services event log. I was getting this error last week:
>
> Event ID 13559
> The File Replication Service has detected that the replica root path has
> changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If
> this is an intentional move then a file with the name
> NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
> This was detected for the following replica set:
> "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
> ......
>
> I did what the error suggested and created a file named
> NTFRS_CMD_FILE_MOVE_ROOT under the root path which stopped the error
> occurring and after that this event was logged on both DC's:
>
> event id 13516:
> The File Replication Service is no longer preventing the computer from
> becoming a domain controller. The system volume has been successfully
> initialized and the Netlogon service has been notified that the system volume
> is now ready to be shared as SYSVOL.
>
> But as yet no sysvol replication has taken place, could it be something to
> do with the Journal being Wrapped? Do i need to do the BurFlags and D2
> procedure?
>
> any help would be great. thanks.

[Luca]

ok im still having this problem. I have checked all ACLs and they are look
to be fine, all services are started, connectivity is good as AD replicates
fine.

I have done a non-authoritative restore on both DCs in the site and still
no sysvol replication. I even tryed an authoritative restore using
directions from this site:
http://support.microsoft.com/default.aspx/kb/290762
but still no replication...

Any other suggestions?? thanks

[Parijat]

Hi,

Please check the amount of disk space you have on the drive where you have
the Sysvol folder. If its too less then you might consider freeing up more
space or moving sysvol to a different drive.

Also put a "canary file" in the scripts folder (Netlogon) and restart the
FRS service on all the domain controllers one at a time and verify if it gets
replicated to other DCs.

Is it like only one DC is not replicating out changes made on it or any
changes made to GPOs in the Sysvol folder on any DC does not trigger a
replication?

If its just with a single DC, I think you would like to get a dcdiag and
netdiag in verbose mode and look for any issues.

Regards,

Parijat...



"Luca" wrote:

> ok im still having this problem. I have checked all ACLs and they are look
> to be fine, all services are started, connectivity is good as AD replicates
> fine.
>
> I have done a non-authoritative restore on both DCs in the site and still
> no sysvol replication. I even tryed an authoritative restore using
> directions from this site:
> http://support.microsoft.com/default.aspx/kb/290762
> but still no replication...
>
> Any other suggestions?? thanks
>
>

[sirrar]

I have had the exact same problem.
My problem was solved by taking a good look at NTFS Junction links.
Take a good look at:
http://support.microsoft.com/kb/315457

Especially this section:
On each domain controller in the domain, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type net start ntfrs to start the File Replication service.
Type ntfrsutl ds |findstr /i "root stage", and then press ENTER. The NTFRSUTIL command returns the current root directory for the SYSVOL replica set that is referred to as the “replica set root” and the staging folder. For example, this command returns:
Root: C:\WINNT\SYSVOL\domain
Stage: C:\WINNT\SYSVOL\staging\domain
Type Linkd %systemroot%\SYSVOL\SYSVOL\ DNS Domain name, and then press ENTER. The LINKD command returns the following:
Source DNS Domain Name is linked to %systemroot%\SYSVOL\domain
Type linkd "%systemroot%\SYSVOL\staging areas\DNS Domain Name", and then press ENTER. This command returns the following:
Source DNS Domain Name is linked to %systemroot%\SYSVOL\Staging\domain
Note The path that is reported by the LINKD command varies depending on the location of the SYSVOL\SYSVOL\DNS Domain Name folder. If the SYSVOL folder is in the default location in the %systemroot%\SYSVOL folder, use the commands that are listed. Otherwise, type the actual path of the SYSVOL folders.

For example, if the NTFRSUTL and LINKD commands are run on a domain controller in the contoso.com domain, and the SYSVOL folder is in the C:\Windows\SYSVOL folder, the command syntax and results for the SYSVOL and Staging folders will appear similar to the following:

C:\>ntfrsutl ds |findstr /i "root stage"
Root: C:\windows\sysvol\domain
Stage: C:\windows\sysvol\staging\domain

C:\>Linkd %systemroot%\SYSVOL\SYSVOL\Contoso.com
Source domain.com is linked to
C:\WINDOWS\SYSVOL\domain

C:\>linkd “%systemroot%\SYSVOL\staging areas>\Contoso.com
Source domain.com is linked to
C:\WINDOWS\SYSVOL\staging\domain



To re-create the junction points if the LINKD command reports missing or invalid junction points, follow these steps:
Type linkd C:\WINNT\SYSVOL\sysvol\DNS_Domain_Name Source, where Source is the root path that is determined by using the NTFRSUTL command.
Type C:\linkd "C:\WINNT\SYSVOL\staging areas\DNS_Domain_Name " Source, where Source is the stage path that is determined by using the NTFRSUTL command.