When you try to reestablish the connection, you may receive the following error message:
When this behavior occurs, the issue is not fixed until you restart SQL Server Services on the secondary replica. In a rare scenario, you may have to restart SQL Server Services on the primary replica to resume Always On data movement.
Note This problem might occur only on very powerful computers and when SQL Server is very busy. For example, in one scenario, this problem occurred on a very busy system with 24 cores.
Article ID: 3213703 - Last Review: 21 mar, 2017 - Revision: 13