Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Assume that you use Always On Availability Groups (AG) in SQL Server 2019. Data movement for some databases of some secondary replicas suddenly stopped (one database for one secondary replica). If one of the impacted secondary replicas is a synchronous replica, long HADR_SYNC_COMMIT waits happen and block transactions to commit. When Trace Flag (TF) 3605 is enabled for extra SQL logging, "LogConsumer::StartScan failed to get the control lock" error occurs and is logged in SQL error log.


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:

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:


Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!