HELP: FAILED ASSERTION

Hello,
I have a concern about 2 errors "Failed Assertion". We're using SQL Server
2005 SP2. May anyone help me to fix these errors?
It says:
SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion =
'!m_updNestedXactCnt' Trying to use the transaction while there are 1
parallel nested xacts outstanding. 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 Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion = 'NULL
== m_lockList.Head ()'. 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.
I would run a checkdb but this is almost always a bug in SQL Server. You
ought to open a case with PSS.
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
> Hello,
> I have a concern about 2 errors "Failed Assertion". We're using SQL Server
> 2005 SP2. May anyone help me to fix these errors?
> It says:
> SQL Server Assertion: File: <"xact.cpp">, line = 2788 Failed Assertion =
> '!m_updNestedXactCnt' Trying to use the transaction while there are 1
> parallel nested xacts outstanding. 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 Assertion: File: <lckmgr.cpp>, line=9421 Failed Assertion =
> 'NULL
> == m_lockList.Head ()'. 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.
>
|||So I have to report these case to PSS. Ok, thanks for the advice.
"jason" wrote:

> I would run a checkdb but this is almost always a bug in SQL Server. You
> ought to open a case with PSS.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
> "Maxim E" <Maxim E@.discussions.microsoft.com> wrote in message
> news:2AE68634-7472-4A4C-96D0-B9CCE260A2BE@.microsoft.com...
>