FIX: 17066 and 3624 errors when you run the sp_refreshview stored procedure in a large batch that performs binary large object-related operations in SQL Server 2008 R2 or in SQL Server 2012

Article translations Article translations
Article ID: 2778479 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 2 fix release.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You execute a large batch of SQL statements in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012.
  • The SQL statements perform a high volume of binary large object (BLOB)-related operations.
  • The SQL statements call the sp_refreshview stored procedure in the batch.
In this scenario, the sp_refreshview stored procedure may fail. When this issue occurs, the following errors are logged in the SQL Server error log:

Error: 17066, Severity: 16, State: 1.
SQL Server Assertion: File: <tmpilb.cpp>, line=3199 Failed Assertion = 'fNoWriters'. 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.

Error: 3624, Severity: 20, State: 1.
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

Error: 17066, Severity: 16, State: 1.
SQL Server Assertion: File: <tmpilb.cpp>, line=3306 Failed Assertion = 'fNoReaderWriterConflict'. 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.

Additionally, the following error may be logged in the SQL Server error log when this issue occurs:

Error: 17066, Severity: 16, State: 1.
SQL Server Assertion: File: <tmpilb.cpp>, line=3306 Failed Assertion = 'fNoReaderWriterConflict'. 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.

Notes
  • This issue does not occur when you call the sp_refreshview stored procedure outside the batch.
  • The sp_refreshview stored procedure fails if it is called against the same view inside the batch.
  • The binary large object-related operations may be implicit. Therefore,this issue is difficult to identify. However, you can identify this issue by using the error messages.

Resolution

Cumulative update information

Cumulative update 6 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 6. 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:
2728897 Cumulative update package 6 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 The SQL Server 2012 builds that were released after SQL Server 2012 was released

Cumulative Update 2 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1
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 SP1 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 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 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 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Status

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

References

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 2778479 - Last Review: February 18, 2013 - Revision: 4.0
Applies to
  • Microsoft SQL Server 2008 R2 Service Pack 2, when used with:
    • Microsoft SQL Server 2008 R2 Datacenter
    • Microsoft SQL Server 2008 R2 Enterprise
    • Microsoft SQL Server 2008 R2 Developer
    • Microsoft SQL Server 2008 R2 Standard
    • Microsoft SQL Server 2008 R2 Workgroup
    • Microsoft SQL Server 2008 R2 Web
    • Microsoft SQL Server 2008 R2 Express
  • SQL Server 2012 Enterprise Core
  • Microsoft SQL Server 2012 Web
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Express
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Developer
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2778479

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com