Share via

File Replication error 1053

Anonymous
2024-05-19T05:50:16+00:00

This domain controller has migrated to using the DFS Replication service to replicate the SYSVOL share. Use of the File Replication Service for replication of non-SYSVOL content sets has been deprecated and therefore, the service has been stopped. The DFS Replication service is recommended for replication of folders, the SYSVOL share on domain controllers and DFS link targets.

Regards,

Mohammad Abed

Windows for business | Windows Server | Directory services | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2024-05-20T06:50:45+00:00

Hi IT Department7,

Thank you for posting in the Microsoft Community Forums.

Error 1053 usually means that a Windows service fails to start within a specified amount of time. Here are some steps you can try to fix this error:

  1. Open the Services console. It can be opened by pressing the "Windows key + R" key combination, typing "services.msc" and pressing the "Enter" key.
  2. Find the service where the error occurred, right-click on it and select Properties.
  3. In the Properties window, click the Login tab.
  4. Make sure the "This Account" option is selected and enter the username and password for the account with administrator privileges.
  5. Click the Apply button, and then click the OK button.
  6. Restart your computer and check if the service has started successfully.

If the above steps can't resolve the issue, try the following steps:

  1. Open the Services console.
  2. Find the service where the error occurred, right-click on it and select Properties.
  3. In the Properties window, click the Dependencies tab.
  4. Make sure that all dependent services are started.
  5. Restart your computer and check if the service has started successfully.

If the problem still persists, try uninstalling and reinstalling the service.

Best regards

Neuvi Jiang

Was this answer helpful?

0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-05-19T17:53:10+00:00

    Yes, well, in addition to my reply in "the other post" (Could you please have one topic and stick with it?) this log file states what I already feared; network connectivity between this DC and others is broken.

    Consider a clean install and instead of migrate to DFS start with it.

    I will be around the coming couple of weeks to see and opinionate on what questions are brought here.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-05-19T06:32:32+00:00

    ADFS

    Log Name: AD FS/Admin Source: AD FS Date: 5/18/2024 9:22:24 PM Event ID: 217 Task Category: None Level: Error Keywords: AD FS User: SYSTEM Computer: SOM-S-ADC.samra.com.jo Description: A WS-Trust endpoint that was configured could not be opened. Additional Data Address: https://somadfs.samra.com.jo/adfs/services/trust/13/windowstransport Mode: WindowsTransport Error: MSIS7207: The ServicePrincipalName of the AD FS account: 'NT AUTHORITY\SYSTEM' could not be retrieved. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 217 0 2 0 0 0x8000000000000001 19919 AD FS/Admin SOM-S-ADC.samra.com.jo http://schemas.microsoft.com/ActiveDirectoryFederationServices/2.0/Events"> https://somadfs.samra.com.jo/adfs/services/trust/13/windowstransport WindowsTransport MSIS7207: The ServicePrincipalName of the AD FS account: 'NT AUTHORITY\SYSTEM' could not be retrieved.

    Regards,

    Mohammad Abed

    Was this answer helpful?

    0 comments No comments