Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mfemenel
Professor Frink
1421 Posts |
 Posted - 2003-12-12 : 09:31:44
|
| I only found a few things in the forum search. Anyone have any further info on this? Google doesn't bring back too much either. Looks like a C issue in SQL2K. We're up to date on service packs.17066 :SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed Assertion = 'm_offBeginVar < m_SizeRec'.Mike"oh, that monkey is going to pay" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-12-12 : 12:23:43
|
| I found this when I searched in MS' knowledge base:http://support.microsoft.com/default.aspx?scid=kb;en-us;317852It mentions applying the latest service pack, but since you already did, just drop and then recreate your index. If your problem has nothing to do with indexes, then you will probably need to contact MS for this (they might already have a hotfix).Tara |
 |
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2003-12-12 : 15:50:16
|
| Thanks for your response. This was a fun one. Here's the response from Microsoft.Resolution:====================================================We noticed that you are using the NOLOCK hint in your SQL Server Stored procedure. Due to the known bug (470213) When the SQL Server engine attempts to search for a row when a query uses the NOLOCK hint or READ UNCOMMITTED (sometimes referred to as a 'dirty read'), there is a chance that the target row may be deleted and may be at that time that record accessed in the query then the query may fail with a retail assertion, and you receive an assertion error message similar to the following: Msg 3624 Location: recbase.cpp:1378 Expression: m_offBeginVar < m_SizeRec In Conclusion: ====================================================We have a hot fix for this issue and the build no for that 857. But before 857 you should have an 818 that is security patch (MS03-039). But we are not recommending that hot fix and security patch at once because you saw that Assertion only one time and after restarting the machine you are ok. The reason for not recommending the MS03-039 immediately is that may be this security patch tightens up some other SQL processes e.g. SQL Agent, SQL mail or may be some connectivity issues. But if you see this error message again then we will go for the hot fix and security patch as well. I am also sending you a PSSDiag and all instructions how to run that tool to capture the issue. If you guys face this issue next time then before restarting the machine run that tool and try to capture the issue and then we will work on the issue.==================================================== Mike"oh, that monkey is going to pay" |
|
|
|
|
|
|
Assertion Error