System Assertion Check failed

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » System Assertion Check failed

System Assertion Check failed

Rate Topic

Display Mode

Topic Options

Author

Message

Chandu-212374

Posted Thursday, October 16, 2008 12:34 AM

Valued Member

Group: General Forum Members
Last Login: Thursday, July 05, 2012 5:23 AM
Points: 65, Visits: 280

On SQL2005 i ran a DB Update script. Among a lot of other things it does (re)create a lot of indexes. On a few indexes we get the following error:

ERROR : 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.

Now i tried DBCC with all different options, but it did not find any corruption.

In an effort to resolve this issue i also applied the latest hotfix, SQLServer2005-KB953752-x86-ENU.exe. This did not fix the problem.

Is this a bug, will we need to have Microsoft have a look at it?

Post #586743

Jimmy.Liew

Posted Monday, June 28, 2010 1:14 AM

SSC Rookie

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 3:50 AM
Points: 26, Visits: 308

I encountered the same error as well. Does anyone has any solution for this? Kindly advice.

Regards,

Jimmy

Post #943694

Preet_S

Posted Friday, October 14, 2011 9:32 AM

SSC Veteran

Group: General Forum Members
Last Login: Wednesday, May 01, 2013 5:15 AM
Points: 236, Visits: 235

Me too.
Getting this error running an INSERT statement with (TABLOCK). Resulting in a Stack dump. The table is NOT compressed/replicated, CHECKDB does not reveal any errors. Using SQL Server 2008 R2 build 10.50.1600.1 (no Service Packs).

Error log excerpts :

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.

SQL Server Assertion: File: <pageref.cpp>, line=922 Failed Assertion = 'IS_OFF (BUF_MINLOGGED, m_buf->bstat) || pageModifyType != PageModifyType_Contents || GetPagePtr ()->IsTextPage ()'. 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.

Post #1190623

GilaMonster

Posted Friday, October 14, 2011 10:42 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:52 AM
Points: 37,734, Visits: 30,001

Call Microsoft Customer Support.

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1190690

« Prev Topic | Next Topic »

Permissions