Select the product you need help with
FIX: "Failed Assertion = 'CheckValidInput (wsName, cbName)'" error when you use database mirroring in Microsoft SQL Server 2008 R2Article ID: 2802113 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 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 1 fix release. On This PageSymptomsThe following error messages may be logged in the SQL Server error log when you use database mirroring and execute an ALTER DATABASE statement in Microsoft SQL Server 2008 R2. Date Time spid# **Dump thread - spid = 0, EC = 0x00000004AADE8B20 Date Time spid# ***Stack Dump being sent to DriveName:\MSSQLSERVER\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt Date Time spid# * ******************************************************************************* Date Time spid# * Date Time spid# * BEGIN STACK DUMP: Date Time spid# * Date Time spid# Date Time spid# * Date Time spid# * Location: DbmConnection.cpp:798 Date Time spid# * Expression: CheckValidInput (wsName, cbName) Date Time spid# * SPID: # Date Time spid# * Process ID: # Date Time spid# Error: 17066, Severity: 16, State: 1. Date Time spid# SQL Server Assertion: File: <DbmConnection.cpp>, line=798 Failed Assertion = 'CheckValidInput (wsName, cbName)'. 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, a mini-dump file is generated when this issue occurs. Note This issue does not occur in Microsoft SQL Server 2012. ResolutionCumulative update informationCumulative Update 6 for SQL Server 2008 R2 Service Pack 2The 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 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:2830140 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 Service Pack 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:
(http://support.microsoft.com/kb/2830140/
)
Cumulative update package 6 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301 /
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was releasedSQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2812683 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 Service Pack 1 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:
(http://support.microsoft.com/kb/2812683/
)
Cumulative update package 11 for SQL Server 2008 R2 Service Pack 12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2802113 - Last Review: April 15, 2013 - Revision: 3.0 Applies to
| Article Translations
 |
Back to the top
