DC fails to replicate after January 2022 & March 2022 Patches

309ra 21 Reputation points
2022-03-22T16:48:37.733+00:00

We have an issue with a DC that is Server 2016. We installed the January 2022 patch and replication started to fail. We know there was an OOB patch, but we didn't apply it. We removed the January 2022 patch and everything worked again. We decided to skip February and installed the SSU and patch for March 2022 and the same issue happened. RPC 1722 server is unavailable error.

We have other Server 2016 DC's that got the same patches and no issues. Has anyone seen this problem?

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2022-03-22T17:18:39.61+00:00

    Dcom errors should be unrelated. If replication fails there should be errors recorded in the event log. Not sure what you're seeing but you could try a non authoritative sync. If using older FRS you can follow along here.
    https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi
    or for DFSR follow along here.
    https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2022-03-22T17:05:33.563+00:00

    What's in the system and DFS Replication event logs?

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.