Select the product you need help with

FIX: "SQL Server Assertion: File: <bcmdsink.cpp>, line=<n> Failed Assertion = 'src'" error message when you update BLOB data in SQL Server 2008 R2 or in SQL Server 2012

Article ID: 2749560 - View products that this article applies to.

Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) update release.

Back to the top | Give Feedback

Symptoms

Consider the following scenario:

You create a table that contains some binary large object (BLOB) data type columns in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012. For example, the table contains a Text data type column.
You create a transactional publication to replicate the columns that are not BLOB data type columns. Then, you create a subscription for the publication.
You create another transactional publication to replicate the BLOB data type columns. Then, you create a subscription for the publication.
You run the UPDATETEXT statement to update the BLOB data on the publisher.

In this scenario, the replication Log Reader Agent fails. Additionally, the following error message is logged in the SQL Server error log file:

Error: 17066, Severity: 16, State: 1
SQL Server Assertion: File: <bcmdsink.cpp>, line=<n> Failed Assertion = 'src'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.

Back to the top | Give Feedback

Resolution

Cumulative update information

Cumulative Update 5 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:

2777772

(http://support.microsoft.com/kb/2777772/ )

Cumulative update package 5 for SQL Server 2012

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2692828

(http://support.microsoft.com/kb/2692828/ )

The SQL Server 2012 builds that were released after SQL Server 2012 was released

Cumulative Update 4 for SQL Server 2008 R2 SP2

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:

2777358

(http://support.microsoft.com/kb/2777358/ )

Cumulative update package 4 for SQL Server 2008 R2 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2730301

(http://support.microsoft.com/kb/2730301/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 9 for SQL Server 2008 R2 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2756574

(http://support.microsoft.com/kb/2756574/LN/ )

Cumulative update package 9 for SQL Server 2008 R2 SP1

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2567616

(http://support.microsoft.com/kb/2567616/LN/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was released

Microsoft SQL Server 2008 R2 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 R2 Service Pack 1 hotfix to an installation of SQL Server 2008 R2 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Back to the top | Give Feedback