Thursday, March 22, 2012

Error: 3624 - SQL Server Assertion

Ok, I keep getting SQL Server assertions in the event log, with the
following stack dump message in the SQL Server logs. Any ideas?
DBCC CHECKDB reveals no problems.
* ----
--
2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is 0x2EF0EDAD
2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
line=573
Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
*Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
*Stack Dump being sent to I:\Microsoft SQL Server\MSSQL\log\SQLDump0033.txt
*
****************************************
************************************
***
Thanks in advance,
Jerry DennanyJerry,
If you search MS site for error 3624, which is mentioned in the stack dump,
you will find plenty of articles
(http://search.microsoft.com/search/...=1&s=0&c=3&st=b
&qu=3624&na=32). There are many possible reasons for this error. Just by
reading the article titles I guess you will be able to narrow the search to
your problem.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Jerry Dennany" <jerry@.dennany.org> wrote in message
news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
>
> Ok, I keep getting SQL Server assertions in the event log, with the
> following stack dump message in the SQL Server logs. Any ideas?
> DBCC CHECKDB reveals no problems.
>
>
* ----
> --
> 2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is
0x2EF0EDAD
> 2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
> line=573
> Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
> 2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
> *Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
> *Stack Dump being sent to I:\Microsoft SQL
Server\MSSQL\log\SQLDump0033.txt
> *
>
****************************************
************************************[vbc
ol=seagreen]
> ***
>
> Thanks in advance,
> Jerry Dennany
>[/vbcol]|||I suppose that I should have mentioned that I've already performed the
typical google and support.microsoft.com searches, without finding anything
applicable. Any other ideas?
Thanks,
Jerry Dennany
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OTZriQGJEHA.3704@.TK2MSFTNGP11.phx.gbl...
> Jerry,
> If you search MS site for error 3624, which is mentioned in the stack
dump,
> you will find plenty of articles
>
(http://search.microsoft.com/search/...=1&s=0&c=3&st=b
> &qu=3624&na=32). There are many possible reasons for this error. Just by
> reading the article titles I guess you will be able to narrow the search
to
> your problem.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Jerry Dennany" <jerry@.dennany.org> wrote in message
> news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
>
* ----
> 0x2EF0EDAD
> Server\MSSQL\log\SQLDump0033.txt
>
****************************************
************************************[vbc
ol=seagreen]
>[/vbcol]|||> I suppose that I should have mentioned that I've already performed the
> typical google and support.microsoft.com searches, without finding
anything
> applicable. Any other ideas?
Sorry, not directly. Maybe you can track down what happens before this
error, which command makes the problem? It would be nice if the problem
would be reproducable.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||The following is the SqlException our code got when that happens. What Jerr
y and I don't understand is that the error message "Duplicate key was ignore
d" should be associated with SQL error 3604, which is only on severity level
16 that will not throw the exception, (while error 3624 is on level 20).
The database table has a composit unique index (Odometer, QueueID) with "Ign
ore duplicate key", and a composit cluster index (QueuedTime, Odometer). Th
e Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual process
ors.
Error: 3624
General message:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlExce
ption:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavio
r, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.
@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in message news:ecsL
MESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> anything
>
> Sorry, not directly. Maybe you can track down what happens before this
> error, which command makes the problem? It would be nice if the problem
> would be reproducable.
>
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
>
>|||Can you send me the code directly to my e-mail (just take out the "_please_r
eply..." part out of the address and I will try to reproduce the error? BTW,
which versions of SQL Server and .NET Framework are you using?
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Yang Cao" <yang@.yangcao88.com> wrote in message news:uu3i%23lUJEHA.3436@.tk2
msftngp13.phx.gbl...
The following is the SqlException our code got when that happens. What Jerr
y and I don't understand is that the error message "Duplicate key was ignore
d" should be associated with SQL error 3604, which is only on severity level
16 that will not throw the exception, (while error 3624 is on level 20).
The database table has a composit unique index (Odometer, QueueID) with "Ign
ore duplicate key", and a composit cluster index (QueuedTime, Odometer). Th
e Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual process
ors.
Error: 3624
General message:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlExce
ption:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavio
r, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.
@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in message news:ecsL
MESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> anything
>
> Sorry, not directly. Maybe you can track down what happens before this
> error, which command makes the problem? It would be nice if the problem
> would be reproducable.
>
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
>
>

No comments:

Post a Comment