Posted on November 2, 2009 by Christoffer Steding This can happen when you convert a physical server to a virtual server. See example of private comment Links: File Replication Service Diagnostics Tool, EventID 13520 from source NtFrs Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links... x 27 Juergen Zeuner If the file NTFRS_CMD_FILE_MOVE_ROOT does not solve the problem and the FRS still logs the event, here is what I did to solve the problem. This security permission can be modified using the Component Services administrative tool. Source
Issue is strange… Exchange Windows Server 2008 Windows Server 2012 Changing the Backup Exec Service Account and Password Video by: Rodney This tutorial will walk an individual through locating and launching The files may or may not be deleted from the old location depending on whether they are needed or not. Please wait for the task to complete. Find the below mentioned article for the same. other
Everything appeared to be ok, except for a strange musical note appended to the end of the "sysvolsysvolfqdn" output. Click Start, and then click Run. 5. What version of SBS? 2. After a reboot, the error went away and 13516 appeared without issue.
Rereading the error above, more slowly this time, it all made perfect sense. Are there any other DCs in the AD? 3. I am an MCSE and support a wide variety of IT-related items at my job, including: Windows OS's, Exchange, Terminal Services, .NET, IIS, OS X, Microsoft Office, printers, phones, Linux, Adobe Ntfrs_cmd_file_move_root Server 2008 Up until then it was all 13501 &13516's which would be indications that things are going well.
If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? When was it taken? Your links are certainly the way to go. official site I haven't been able to find any answer as to why it did. 0 Featured Post Comprehensive Backup Solutions for Microsoft Promoted by Acronis Acronis protects the complete Microsoft technology stack:
We can not find any KB with instruction on how we should proceed. Put Empty File "ntfrs_cmd_file_move_root" Into The Root Of The Replica Hopefully some of the solutions I find throughout the workday are useful to you as well Thursday, December 30, 2010 Fix event ID 13559 problem on a Windows server After migrating The files may or may not be deleted from the old location depending on whether they are needed or not. x 36 Gil Davidman I had this event when I converted my server to VMWare ESXi (backup physical server & restored as VM).
Create a file named NTFRS_CMD_FILE_MOVE_ROOT in the directory listed in the event description where the replica root path has been moved to. this website x 36 Adam Bell I also followed the directions to create the NTFRS_CMD_FILE_MOVE_ROOT file and it worked perfectly. Ntfrs_cmd_file_move_root MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store Headlines Website Testing Ask a Question How To Create Ntfrs_cmd_file_move_root Any help would be greatly appreciated.
Privacy statement © 2017 Microsoft. http://3swindows.com/event-id/file-share-witness-resource-failed-to-arbitrate-for-the-file-share.html This re-addition will trigger a full tree sync for the replica set. We have not moved the path for any replica sets. Click Start, and then click Run. 2. Event Id 13559 Ntfrs Windows 2008
This re-addition will trigger a full tree sync for the replica set. To be fair, a reboot should not fix this issue. Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? http://3swindows.com/event-id/ntfrs-13508-server-2012-r2.html Say like in an SBS2003 environment?
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. Ntfrs Error Event 13559 Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13559 Date: 2009-11-01 Time: 16:45:41 User: N/A Computer: compit-srv01Description: The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If you only have 1 then you shouldn't be having any replication problems since there is nowhere to replicate to.
Allow some time (more than 10 minutes) for the system to replicate the GPOs from the primary DC. Saturday, January 07, 2012 11:59 AM Reply | Quote 0 Sign in to vote Please run the SBS BPA and post back the results. After checking the directory service event logs I found repeated entries for event ID 13359, stating "The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" Event 13508 Examine the services.
The files may or may not be deleted from the old location depending on whether they are needed or not. There's also KB 819268, but I didn't really find it useful. Comments: Anonymous In our case this issue occured when we virtualized one of the two Windows 2003 domain controllers with VMWare converter tool. Check This Out x 86 EventID.Net You may notice that the %SystemRoot%\Sysvol\
I even waited a couple of days and rebooted again and it was still fixed. Additional error information from SQL Server is included below. Create the file NTFRS_CMD_FILE_MOVE_ROOT in the new "domain" folder. Upon initial examination, I ran across this error in the event logs: NtFrs Event Details: The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain".
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13559
NtFrs Event Details: The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain".