none
Bizzare Random Error When Running A SQL Job (Error 3624)

    Question

  • I have a T-SQL job that runs a stored proc that accepts two arguments. Periodically I get the following error:

    Unspecified error occurred on SQL Server. Connection may have been terminated by the server. [SQLSTATE HY000] (Error 0)  A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. [SQLSTATE HY000] (Error 3624)  Location:  "xact.cpp":4253 Expression:  !m_parNestedXactCnt SPID:   61 Process ID:  2120 Description:  Trying to use the transaction while there are 1 parallel nested xacts outstanding [SQLSTATE 01000] (Error 3624)  Location:  "xact.cpp":4362 Expression:  !m_parNestedXactCnt SPID:   61 Process ID:  2120 Description:  Trying to use the transaction while there are 1 parallel nested xacts outstanding [SQLSTATE 01000] (Error 3624).

    I have done the DBCC CHECKDB with the Repair Rebuild options and it found no errors. Has anyone else had this error before? I'm runnning Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   Mar 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1) 

     (Yup 64 bit SQL 2008 on 64 bit Windows 2008... beefy box :D )


    DJ Baby Anne's Biggest Fan................
    Wednesday, June 02, 2010 1:20 PM

Answers

All replies

  • Hi,

    Try to install the last Cumulative Update 8 for SQL Server 2008 Service Pack 1:
    http://support.microsoft.com/kb/981702

    If it doesn’t fix this issue, you may consider to contact Microsoft Customer Support Services (CSS) to open a case for dump analysis which should be the best way to identify the root cause of this issue I think.

    If you have any more questions, please let me know.
    Thanks.


    ***Xiao Min Tan***Microsoft Online Community***
    Friday, June 04, 2010 8:14 AM
    Moderator
  • I only have one. How do we send the dump from SQL Server. I see some sort of module dump in the SQL Error Log. Is that what they typically ask for?
    DJ Baby Anne's Biggest Fan................
    Monday, June 07, 2010 1:58 AM
  • Hi,

    You could collect a full dump file and contact CSS (http://support.microsoft.com) for further analysis. To collect a full dump file, you can refer to this article, http://support.microsoft.com/kb/917825.

    If you have any more questions, please let me know.
    Thanks.


    ***Xiao Min Tan***Microsoft Online Community***
    Monday, June 07, 2010 3:16 AM
    Moderator