Assume that you use Microsoft SQL Server 2016. When you try to initialize multiple databases in a SQL Server Always On availability group (AG) by using automatic seeding, you notice that seeding for some databases may fail, and need to retry on one or more secondary replicas.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
To work around this issue, you can retry on one or more secondary replicas, use backup or use restore for initialization.