You are currently viewing Tips For Resolving The File Replication Service Is In Error 13555

Tips For Resolving The File Replication Service Is In Error 13555

 

Updated

  • 1. Download ASR Pro
  • 2. Run the program
  • 3. Click "Scan Now" to find and remove any viruses on your computer
  • Speed up your computer today with this simple download.

    This article will identify some of the potential causes that can lead to the file replication service error 13555, and then presents possible solutions to try to resolve the issue.

     

     

    • Read 4 minutes

    This article helps resolve an issue where the SYSVOL directory is not replicated between domain controllers that are still running Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003.

    Applies to: Windows Server 2019, Windows Server 2016, Windows Server 2012 R2
    Original Knowledge Base Number: 2986364

    Symptoms

    This issue can occur on a domain controller that typically runs Windows Server under any of the following conditions:

    • You are changing the layout of system devices or the configuration related to system devices does not work.
    • A file replication service (FRS) database corruption has occurred.

    Event 13555:
    FRS is indeed in error

    Event 13552:
    FRS cannot add this person to the following replica set: “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”

    These event logs indicate that the SYSVOL folder is not replicated between domain controllers. Thus, this incompatible problem leads to ourGroup Policy triples, and the wrong policy decision is detected on each client computer.

    Reason

    This submission occurs because NTFS recognizes the firmware processing as a configuration change on the storage medium and then changes the journal ID. Therefore, the specific ID file for the FRS database data does not match the ID file because of the wide range of USN log database data.

    Workaround

    To avoid this problem, events in domains that controllers register can be logged as follows:

    1. the file replication service is in an error state 13555

      Perform a full or application state backup for each domain controller.

    2. Stop this FRS service. To do this, use the Swift command on each domain controller to type each of the following, and then press ENTER: net stop ntfrs

      Note

      In this step, select a personal reference domain controller that may depend onconnections and physical resources of the server. This regulatory area will become the “reference regulatory area” in all subsequent stages.

    3. Updated

      Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!


      Delete the files in the following three folders to initialize FRS on the reference domain controller.
      Do not delete the three folders at this time. Delete subfolders and files in these three folders:

      • % systemroot% ntfrs jet
      • % systemroot% sysvol domain DO_NOT_REMOVE_NtFrs_PreInstall_Directory
      • % systemroot% sysvol staging domain If you do not see these folders and documents, follow the additional steps to discover hidden files or folders .
    4. Force synchronization with FRS on the reference domain governor. To do this, follow these steps:

      1. Open this registry editor and locate the following computer subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet SERVICES NTFRS Parameters Backup / Restore Process at startup
      2. Right-click the BurFlags entry, then click Edit.
      3. Enter D4 in the Value field and just click OK.
      4. Close the registry editor.
    5. On command, the reference domain controller quickly executesRun the Once command to restart FRS: net start out ntfrs

      Note

      Steps 6 through 10 should only exist on other domain controllers.

    6. Download the PsTools tool and install it on other blog controllers. This tool includes PsExec. I would say you can use the line tools command Delete folders in the SYSVOL.Files folder

    7. Delete the dynamic files in the three folders below to initialize each FRS on other domain controllers.
      Don’t delete your current three folders. Remove subfolders and files from the following folders:

      • % systemroot% ntfrs jet
      • % systemroot% sysvol domain DO_NOT_REMOVE_NtFrs_PreInstall_Directory
      • % systemroot% sysvol staging domain If three of these additional folders and files are not visible, additionally consider showing hidden files or only folders .
    8. Delete the following folders in “% systemroot% sysvol domain” in the specified path:

      • % systemroot% sysvol domain policy
      • % systemroot% sysvol domain scripts
      • % systemroot% sysvol domain policy_NTFRS_xxxxxxxx
      • % systemroot% sysvol domain scripts_NTFRS_ xxxxxxx
      • % systemroot% sysvol domain NtFrs_PreExisting__See_Evntlog

      Note

      “xxxxxxx” is a placeholder that evaluates alphanumeric characters. Skip this step if you do not currently have such folders and files.

      Also, if the files in the folder cannot be deleted, follow these steps to delete them using the PsExec tool.

      Steps to delete files and files using the PsExec tool:

      1. Run Command Prompt as Administrator.
      2. Replace the current directory list with the drive where the PsTools installation files are located (for example, start the c: PsTools drive).
      3. Run the following command: Psexec.exe -i -verts cmd .
      4. In a new prompt, enter road / s to remove the following files and versions in the SYSVOL folder (for example, run rd% systemroot% sysvol domain Policies / s):
        • % systemroot% sysvol domain policy
        • % systemroot% sysvol domain scripts
        • % systemroot% sysvol domain policy_NTFRS_xxxxxxxx
        • % systemroot% sysvol domain scripts_NTFRS_ xxxxxxx
        • % systemroot% sysvol domain NtFrs_PreExisting__See_Evntlog

      Note

      “xxxxxxx” is an actual placeholder representing alphanumeric characters. Ignore this step when these versions and file do not exist.

    9. Force FRS synchronization on additional domain controllers. To do this, follow these steps:

      1. Open Registry Editor and locate the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet SERVICES NTFRS Parameters Backup / Restore Process at startup
      2. Right-click the BurFlags entry, then click Edit.
      3. Enter D2 in the value data field, then click OK.
      4. Close the registry editor.
    10. At the command line, hurry to restart FRS with other domain controllers: net start ntfrs

    11. Confirm replication often.

      • “Error”, “Warning” or log entries will not be written to the event log at this time. Event ID 13516 is typically logged when replication is successful.
      • Check for consistency by comparing SYSVOL files and folders in files across all site controllers.
    12. Restart FRS on the reference controller network by running the following command: net Conquer ntfrs && net start ntfrs

    After completing all of the above, review the FRS Events document… Events 13553, IDs 13554 and 13516 were logged within minutes. These logs show that SYSVOL replication completed successfully.

    Status

    the file replication service is in an error state 13555

    Microsoft, in turn, has confirmed that there is an issue with Microsoft products, which are clearly listed in the “Applies to” section.

    Additional Information

    1. In Windows Explorer, click Folder Options on the Tools menu.

    2. On the View tab, enable Show Hidden Files Folder.

      Note

      For Server Windows 2012 R2, Server Windows 2012, or Server Windows 2008 R2, enable Show files, folders, and more. hidden in the View tab.

    Please follow the instructions in this section carefully. Serious problems can occur if you modify the PC registry incorrectly. Before changing them, reset the registry to recover in case of difficulty.

    In this step, we have selected a reference desktop controller, which may depend on the Internet connection and the physical resources of the server. This control room will be the “reference domain of the controller” for all softwarenext steps 6.

    Step 10 should only be performed on other site name controllers.

    “xxxxxxx” is an alphanumeric placeholder. Skip this step if these folders and files do not exist.

    “xxxxxxx” are alphanumeric characters. This step should be skipped if such files and files do not exist.

    • The domain controller indicates that “BurFlags means D4” acts as a reference domain controller until the service is permanently restarted. The BurFlags of the input is cleared by restarting the FRS.
    • For domain controllers with “BurFlags = D2”, the BurFlags entry will also be automatically reset when FRS is restarted.

    In Windows Server 2012 R2, Windows Server 2012, or just Windows Server 2008, enable r2, the Show hidden files, folders and drives option on the View tab.

     

     

    Speed up your computer today with this simple download.

     

     

     

    Filreplikeringstjänsten är I Ett Feltillstånd 13555
    파일 복제 서비스가 오류 상태에 있음 13555
    Le Service De Réplication De Fichiers Est Dans Un état D’erreur 13555
    Il Servizio Di Replica File è In Uno Stato Di Errore 13555
    O Serviço De Replicação De Arquivos Está Em Estado De Erro 13555
    Служба репликации файлов находится в состоянии ошибки 13555
    El Servicio De Replicación De Archivos Tiene Un Estado De Error 13555
    Usługa Replikacji Plików Jest W Stanie Błędu 13555
    De Bestandsreplicatieservice Bevindt Zich In Een Foutstatus 13555
    Der Dateireplikationsdienst Befindet Sich In Einem Fehlerzustand 13555