I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
|||Yes. The two errors are exactly as described. I looked at the dump file and the query was a SELECT against a table with historical data only (in this instance anyway). Basically it is a sales history table and the query sums the sales for a particular salesman month to date. The table is only updated during the end of day processing, when no one else is using he system.
"TJ" <tunj@.hotmail.com> wrote in message news:uzWMgSlsEHA.2196@.TK2MSFTNGP14.phx.gbl...
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment