Assume that you use Transactional replication in SQL Server 2016 or 2017 with Microsoft Azure SQL Database (DB) Subscriber, and you use multiple subscription streams. With this configuration, when there's a deadlock between the different subscription streams, the Distribution Agent will try to roll back all open transactions, and there will be a retry in single subscription mode. In this situation, you may see an intermittent "row not found" error at the Subscriber.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Cumulative Update Information:

This fix is included in the following cumulative updates 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:

On-Demand Hotfix Information:

This issue is fixed in the following on-demand hotfix for SQL Server:


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

Need more help?

Expand your skills


Get new features first


Was this information helpful?

What affected your experience?

Thank you for your feedback!