Avatar of Lanee Kirby
Lanee Kirby
Flag for United States of America asked on

Windows Server 2003 replica root path moved

I am getting Event ID 13559 on one of my AD servers.  The message says,

" 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)"
 
Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.
 
 [1] At the first poll which will occur in 60 minutes this computer will be deleted from the replica set.
 [2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not."

What happened was that I had to use a utility to merge two partitions together because my C:\ was getting so low on space and the server did not like this.  This folder and files actually has not moved at all.  For some reason the server thinks it has and it generates this message.

If I open AD Sites and Services and try to replicate to my other AD server, it seems to works fine and then same results from the other server.  However I am having and issue with my Group policies.

Any ideas on how to resolve this?

Thanks!
Microsoft Server AppsActive DirectoryWindows Server 2003

Avatar of undefined
Last Comment
Sandesh Dubey

8/22/2022 - Mon
Sandesh Dubey

You need to create file NTFRS_CMD_FILE_MOVE_ROOT with no extention in c:\windows\sysvol\domain and restart the FRS service in the event itself the resolution is given once done check the FRS log event id 13516 should occur.Also cross check the health of dc by running dcdiag and repadmin /replsum and post the log  if error is reported.
Lanee Kirby

ASKER
That directory already has a folder with that name and when I try to create a file with that name, no extension, of course it says one already exists.  I have stopped and restarted the FRS service and get the same error but my AD servers are replicating, at least AD Sites and Services indicates they are.  Should I delete that folder and recreate it?
ASKER CERTIFIED SOLUTION
Sandesh Dubey

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Your help has saved me hundreds of hours of internet surfing.
fblack61