Question

jangapi on Fri, 27 Mar 2015 01:05:15


I see this error: Error: 3624, Severity: 20, State: 1

Complete error in the error log is:

SQL Server Assertion: File: <loglock.cpp>, line=807 Failed Assertion = 'result == LCK_OK'. 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.

SQL Server 2008 R2 with Service pack 2 installed and mirrored.

I see this error in the sql server dump file:

0:000> .ecxr
rax=00000000676a7a6a rbx=0000000003fd3250 rcx=000000001048aaa0
rdx=0000000000000000 rsi=0000000003bbef3c rdi=0000000000000440
rip=000007fefd10940d rsp=000000001048b0b0 rbp=000000001048ca50
 r8=0000000000000000  r9=0000000000000000 r10=00000000c000007c
r11=00000000012e98d0 r12=00000000000007c0 r13=0000000000000000
r14=0000000000000000 r15=00000000000007c0
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206
KERNELBASE!RaiseException+0x39:
000007fe`fd10940d 4881c4c8000000  add     rsp,0C8h
0:000> kC  1000
Call Site
KERNELBASE!RaiseException
sqlservr!CDmpDump::Dump
sqlservr!SQLDumperLibraryInvoke
sqlservr!CImageHelper::DoMiniDump
sqlservr!stackTrace
sqlservr!utassert_fail
sqlservr!LogLockCollectionAcquire::Callback
sqlservr!LogLockCollection::ApplyLocks
sqlservr!LogLockCollection::Acquire
sqlservr!DBMRedoManager::AnalyzeLogRecord
sqlservr!DBMRedoManager::RunAnalysis
sqlservr!DBMRedoManager::ApplyLogSegment
sqlservr!DBMRedoManager::Execute
sqlservr!SubprocEntrypoint
sqlservr!SOS_Task::Param::Execute
sqlservr!SOS_Scheduler::RunTask
sqlservr!SOS_Scheduler::ProcessTasks
sqlservr!SchedulerManager::WorkerEntryPoint
sqlservr!SystemThread::RunWorker
sqlservr!SystemThreadDispatcher::ProcessWorker
sqlservr!SchedulerManager::ThreadEntryPoint
msvcr80!endthreadex
msvcr80!endthreadex
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart

Not sure what to infer from this. Any help would be appreciated.

Let me know if more info. is needed.

Thanks !!!

Replies

bhanu_nz on Fri, 27 Mar 2015 01:44:22


Hi,

Please see this link and patch your server accordingly

http://support.microsoft.com/en-us/kb/980832

Thanks

Bhanu

Shanky_621 on Fri, 27 Mar 2015 05:13:30


Assertion error are generally bugs and fixed in Service pack release. Make sure you patch your server with latest Service pack

Did you ran DBCC checkdb (db_name) to make sure there is no corruption in database ?

jangapi on Fri, 27 Mar 2015 17:29:15


I have read this KB article before posting this here, the problem is this is not the exact error that I am seeing.

error: 3624, Severity: 20, State: 1

is very generic and can happen for any reason. Theirs has something to do with a particular query they ran. I would like to understand what this means.

sqlservr!utassert_fail
sqlservr!LogLockCollectionAcquire::Callback

jangapi on Fri, 27 Mar 2015 17:30:57


I did not have a chance to run that at the time the error happened, now everything is normal. Do you have any idea on what this means?

sqlservr!LogLockCollectionAcquire::Callback

Shanky_621 on Fri, 27 Mar 2015 17:49:31


I did not have a chance to run that at the time the error happened, now everything is normal. Do you have any idea on what this means?

sqlservr!LogLockCollectionAcquire::Callback


I suggest you to run full DBCC CHECKDB , like I said assertion errors are basically related to Internal SQL Server problem

Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

My Technet Wiki Article

MVP


Jason_Clark03 on Tue, 24 Apr 2018 12:48:09


Run DBCC CHECKDB and then DBCC CHECKTABLE which provide you more detail about the error and help in troubleshooting that error.

Argenis Fernandez on Tue, 24 Apr 2018 15:48:59


I'd suggest you upgrade to a supported build of SQL 2008 R2, such as out latest published build:

https://support.microsoft.com/en-us/help/4057113/security-update-for-vulnerabilities-in-sql-server

Tons of related issues were corrected between the build that you're using and our latest, supported build.