Assume that you use Distributed AlwaysOn Availability Group (DAG) environment in Microsoft SQL Server 2016 or 2017. If the global primary has a local secondary replica defined and you try to use the defined secondary replica to alter DAG SEEDING_MODE, you may receive an error message that resembles the following:
Msg 41168, Level 16, State 2, Line Line Number
An error occurred while attempting to access availability replica with ID 'ID Number'in availability group 'Group Name'. The availability replica is not found in the availability group configuration. Verify that the availability group name and availability replica ID are correct, then retry the command.
This issue is fixed in the following cumulative updates for SQL Server:
Cumulative Update 18 for SQL Server 2017
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.