How To Fix Frs Error 13559

It looks like some of our readers have encountered a known error called frs error 13559. This issue occurs for a number of reasons. Let’s discuss it now.

Recommended: Fortect

This article describes an issue where NTFRS generates a fatal error when intermittent communication with the entire file system. For:

is for Windows Server 2012 R2
Original Knowledge Base Number: 2768745

Symptom

You can get 13,559 File Replication Service (FRS) events on different domain controllers for similar information:

Protocol name: File Replication Service
Source: NtFrs
Event ID: 13559
Task category: none
Level: Error
Description:
FRS has detected that the replica root suggestions have changed from c: windows sysvol domain to c: windows sysvol domain. If this is an intentional move, a file named NTFRS_CMD_FILE_MOVE_ROOT must be created under the appropriate new root path.
This turned out to be suitable for the following set:
“SYSTEM VOLUME of the domain replica (SYSVOL SHARE)”
Changing the focus of a replica root is a two-step process triggered by the assembly associated with NTFRS_CMD_FILE_MOVE_ROOT.
[1] First, any requests that will be made on this computer are blackIn a few minutes, they will be removed from the replica set.
[2] In this query below, deleting this laptop or this computer with a new root course will be added back to the mock set. This addition triggers a rich tree sync to play the corresponding set. When the connection is complete, all files will be downloaded from the new location. Files may or may not be removed from the old location depending on whether you need them or not.

This is definitely a level 4 logging example to support the ntfrs verbosity that causes Get Together 13559 to log:

: S: Oid for the replica root is 00000000-0000-0000-0000000000000000
ERROR – Mismatch GUID for replica base problems for replica set (DOMAIN SYSTEM VOLUME (SYSVOL SHARE))
ERROR – root guid (FS) of the replica (17358178-8dd7-47e5-8ec1642bbc6ba318) ERROR 2) Replica root ID (DB) (17358178-8dd7-47e5-8ec1642bbc6ba318) ERROR – the replica record (DOMAIN SYSTEM VOLUME (SYSVOL SHARE)) is likely to be marked for deletion

We have seenand have seen cases where the filesystem GUID was reported as NULL on the second debug print:

: S: Oid for the replica root is usually 00000000-0000-0000-0000000000000000
ERROR – Replica Root ID GUID Mismatch for Replica Set (DOMAIN SYSTEM VOLUME (SYSVOL SHARE))
ERROR – GUID for Base Replica (FS) Issues (00000000-0000-0000-0000000000000000)
ERROR – guid root replica (DB) (17358178-8dd7-47e5-8ec1642bbc6ba318)
ERROR – replica record (DOMAIN SYSTEM VOLUME (SYSVOL SHARE)) marked as deleted

You must keep a level 4 log to be surprised that you are facing this incredible problem.

Reason

In the query loop, the root folder GUID that is returned directly from NTFS does not match. The volume GUID is considered “00000000-0000-0000-0000000000000000”. Although FRS uses synchronous I / O, NTFS I / O control works asynchronously. If there is a problem, the I / O control returns with the message “STATUS_PENDING”, but this state is far from being used correctly by NTFRS.

Resolution

NTFRS is absolutely essential forWindows Server 2003 domain controllers support. Since support for Windows Server 2003 ends in July 2015, we recommend that you completely remove some of these domain controllers and upgrade to a newer version of Windows.

New Windows types allow DFS-R to be used for SYSVOL replication, and none of them are prone to specific issues.

1. Create a started task and event 13559 and restart this particular service

   To create a script that runs on show 13559 that restarts NTFRS plans, follow these steps:

   1. In Event Viewer, you receive event 13559 with the right mouse button, and it is possible. There is an entry Attach task to this event …:

   2. You will be redirected to our main new task wizard and pre-fill the parameters to run a dependent task for the selected event. Thus, you can view many wizard pages.

   3. You must specify a standard action to start the program:

   4. For this special task, you have a short script that is used to restart NTFRS:

   5. 

      Enter the script as the program to run:

   6. This approach requests operations from NTFRS without authoritative recovery.

2. 

   Place an empty directory “NTFRS_CMD_FILE_MOVE_ROOT” in the root directory of its replica

   If a GUID mismatch is found, NTFRS will check for these files to determine if it was intended. If it understands the file, it will save 13560 correctly and start a permanent unauthorized restore from NTFRS.

   For SYSVOL, specify the target folder for, I would say, connections in the SYSVOL shared folder, for example c: windows sysvol domain.

   Recommended: Fortect

   Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

3. 1. Download and install Fortect
4. 2. Open the program and click "Scan"
5. 3. Click "Repair" to start the repair process