January 13, 2011 at 1:00 am
Hi,
I got the fatal error message as
" 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. "
Then i verified the sql server log found the below errors
Error 1:
2011-01-12 10:46:38 - ! The local host server is not running
2011-01-12 10:46:44 - + AutoRestart: The MSSQLSERVER service was successfully restarted
Error 2:
SQL Server Assertion: File: <E:\sql9_sp2_t\sqltdbms\storeng\dfs\manager\lckmgrp.h>, line=675 Failed Assertion = 'm_iteratorInSafeState'. 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 3:
SQL stack dump also generated.
But i could not find any reason for this error message and also i verified the database by running checkdb ,its look good .
Can anyone explain what could be the reason for this failure and solution ?
January 13, 2011 at 3:11 am
Call Microsoft customer support and log a case. Just make sure you're on the highest service pack first.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 13, 2011 at 8:42 am
http://support.microsoft.com/kb/972511
VSTS bug number | KB article number | Description
308815 970726 (http://support.microsoft.com/kb/970726/ ) FIX: Error
message when you try to rebuild one partition of an index on
an indexed view in SQL Server 2005: "A system assertion
check has failed. Check the SQL Server error log for details."
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply