KB4508472 - FIX: Intermittent "row not found" error at Azure SQL DB Subscriber caused by duplication of BEGIN TRAN statements

Work anywhere from any device with Microsoft 365

Upgrade to Microsoft 365 to work anywhere with the latest features and updates.

Upgrade now

Symptoms

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.

Status

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

Resolution

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:

References

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×