Avatar of robklubs
robklubs
Flag for United States of America asked on

Event 13559 on SBS 2011 NTFRS_CMD_FILE_MOVE_ROOT

Hello experts,

I have a SBS 2011 box that was migrated from 2003 about one year ago. About a week ago, Event ID 13559 appeared in the File Replication Service event viewer. Up until then it was all 13501 & 13516's which would be indications that things are going well. Here is the Event 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)"
 
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 5 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.


Nothing was moved on this server, nor was anything virtualized as I've seen as the culprit on other articles. Disk space is fine, and this event just appeared in the middle of the day, approx. 12:02 PM local time.

I'm very reluctant to follow the Event's suggested fix as there are no other DC's to replicate from. SBS 2011 is the only one on the network. I've seen other suggestions about restarting NTFRS but am very reluctant.

Any help would be greatly appreciated.

Thanks,

Rob
SBSWindows Server 2008Microsoft Server OS

Avatar of undefined
Last Comment
robklubs

8/22/2022 - Mon
robklubs

ASKER
I should note, that I haven't even tried to restart the file replication service yet. Not sure what would happen with that event hanging out there.

Looking forward to some guidance!
SOLUTION
Neeraj Kumar

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
ASKER CERTIFIED SOLUTION
robklubs

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
robklubs

ASKER
FYI - I should have given this expert an "A" grade and am looking into how to change it . . . .
robklubs

ASKER
The expert was quick, courteous, and correct. The only reason for the B instead of the A was that a reboot on another machine with the same issue fixed the issue before his solution was needed.

To be fair, a reboot should not fix this issue. I haven't been able to find any answer as to why it did.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck