SQL Server is terminating because of fatal exception e06d7363
-
We are using SQL Server 2005 standard edition 32 bit Microsoft Windows NT 5.2 (3790),NT INTEL X86
My server was down. Message from the log:
SQL Server is terminating because of fatal exception e06d7363. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
Why this happend?
Thank you
-
This is the rest of the error log message:
Login succeeded for user 'USCti\svc_MOS'. Connection: trusted. [CLIENT: 10.10.5.67]
2011-02-21 22:00:50.17 Server CImageHelper::Init () Version-specific dbghelp.dll is not used
2011-02-21 22:00:50.18 Server CImageHelper::Init () Failed load of dbghelp.dll - Not enough storage is available to process this command.
2011-02-21 22:00:50.19 Server **Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
2011-02-21 22:00:50.20 Server CImageHelper::Init () Version-specific dbghelp.dll is not used
2011-02-21 22:00:50.20 Server CImageHelper::Init () Failed load of dbghelp.dll - Not enough storage is available to process this command.
2011-02-21 22:00:50.20 Server ***Symbol load failed - Proceed to dump without any symbols
2011-02-21 22:00:50.21 Server * *******************************************************************************
2011-02-21 22:00:50.21 Server *
2011-02-21 22:00:50.21 Server * BEGIN STACK DUMP:
2011-02-21 22:00:50.21 Server * 02/21/11 22:00:50 spid 0
2011-02-21 22:00:50.21 Server *
2011-02-21 22:00:50.21 Server * ex_handle_except encountered exception E06D7363 - Server terminating
2011-02-21 22:00:50.21 Server *
2011-02-21 22:00:50.21 Server *
* MODULE LISTING:
*
2011-02-21 22:00:50.21 Server * MODULE BASE END SIZE
2011-02-21 22:00:50.21 Server *
* PROCESSOR SPECIFIC CONTEXT:
*
2011-02-21 22:00:50.21 Server * Edi: 00000000:
2011-02-21 22:00:50.21 Server * Esi: 00000000:
2011-02-21 22:00:50.21 Server * Eax: 1ECDE6B0: 000042AC 00000000 00000000 77E4BEF7 00000000 000D0178
2011-02-21 22:00:50.21 Server * Ebx: 0000003F:
2011-02-21 22:00:50.21 Server * Ecx: 1ECDED20: 00000000 00010007 00000000 00000000 00000000 00000000
2011-02-21 22:00:50.21 Server * Edx: 0000003D:
2011-02-21 22:00:50.21 Server * Eip: 77E4BEF7: 10C2C95E 01093D00 840FC000 00000095 F29DE950 9090FFFF
2011-02-21 22:00:50.21 Server * Ebp: 1ECDE700: 1ECDE744 021AE24C 000042AC 00000000 00000000 00000000
2011-02-21 22:00:50.21 Server * SegCs: 7813001B: 00000000 00000000 00000000 00000000 00000000 00000000
2011-02-21 22:00:50.21 Server * EFlags: 00000246:
2011-02-21 22:00:50.21 Server * Esp: 1ECDE6AC: 00000000 000042AC 00000000 00000000 77E4BEF7 00000000
2011-02-21 22:00:50.21 Server * SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000 00000000
2011-02-21 22:00:50.21 Server * *******************************************************************************
2011-02-21 22:00:50.21 Server * -------------------------------------------------------------------------------
2011-02-21 22:00:50.21 Server * Short Stack Dump
2011-02-21 22:00:50.21 Server 77E4BEF7 Module(UNKNOWN+00000000)
2011-02-21 22:00:50.21 Server 021AE24C Module(UNKNOWN+00000000)
2011-02-21 22:00:50.21 Server 021B2160 Module(UNKNOWN+00000000)
2011-02-21 22:00:50.22 Logon Login succeeded for user 'USCti\svc_MOS'. Connection: trusted. [CLIENT: 10.10.5.67]
2011-02-21 22:00:50.22 Server 021B1D0D Module(UNKNOWN+00000000)
2011-02-21 22:00:50.22 Server 02422369 Module(UNKNOWN+00000000)
2011-02-21 22:00:50.22 Server 77E761B7 Module(UNKNOWN+00000000)
2011-02-21 22:00:50.22 Server 77E792A3 Module(UNKNOWN+00000000)
2011-02-21 22:00:50.22 Server Stack Signature for the dump is 0x1A38D65C
2011-02-21 22:00:50.34 Logon Login succeeded for user 'USCti\svc_MOS'. Connection: trusted. [CLIENT: 10.10.5.67]
2011-02-21 22:00:50.44 Server External dump process not executed.
2011-02-21 22:00:50.44 Server DoMiniDump () encountered error (0x80070008) - Not enough storage is available to process this command.
2011-02-21 22:00:50.45 Logon Login succeeded for user 'USCti\svc_MOS'. Connection: trusted. [CLIENT: 10.10.5.67]
2011-02-21 22:00:50.58 Logon Error: 17189, Severity: 16, State: 1.
2011-02-21 22:00:50.58 Logon SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: 10.10.5.67]
2011-02-21 22:00:50.60 Logon Error: 17189, Severity: 16, State: 1.
2011-02-21 22:00:50.60 Logon SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: 10.10.5.67]
2011-02-21 22:00:50.64 Logon Error: 17189, Severity: 16, State: 1.
2011-02-21 22:00:50.64 Logon SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: 10.10.5.69]
2011-02-21 22:00:50.65 Logon Error: 17189, Severity: 16, State: 1.
2011-02-21 22:00:50.65 Logon SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: 10.10.5.69]
2011-02-21 22:00:50.66 Logon Error: 17189, Severity: 16, State: 1.
2011-02-21 22:00:50.66 Logon SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: 10.10.5.69]
2011-02-21 22:00:50.66 Logon Error: 17189, Severity: 16, State: 1.
2011-02-21 22:00:50.66 Logon SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: 10.10.5.69]
2011-02-21 22:00:50.79 Logon Error: 17188, Severity: 16, State: 1.
2011-02-21 22:00:50.79 Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: 10.10.5.67]
2011-02-21 22:00:50.79 Logon Error: 17188, Severity: 16, State: 1.
2011-02-21 22:00:50.79 Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: 10.10.5.67]
2011-02-21 22:00:50.79 Server The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0xe, state: 4. Administrator should deregister this SPN manually to avoid client authentication errors.
2011-02-21 22:00:51.03 Logon Error: 17188, Severity: 16, State: 1.
2011-02-21 22:00:51.03 Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: 10.10.5.60]
-
From the error message it appears that the SQL Server is under memory pressure and was not even able load "dbghelp.dll" which is required for generating the dump files.
It would suggest getting in touch with Microsoft PSS and they would be able to analyze the dump file usually located in the folder hosting the SQL Server Error Log.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga -
I never had experience to contact them, is it a DBA or network admin need to deal with this situation?Thank you
-
The DBA has to contact MS PSS in this case. You may find this link useful in contacting PSS.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga -
Is this nessary to contact Microsoft Support, this is a new company for me and I am not sure if they have account with them. Thank you
-
AFAIK, it is easier for the PSS engineers to analyze the mdmp files and there are some symbols which are not available to everyone.
Since I am not an expert in analyzing mdmp files, I would reach out to PSS
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga -
Thank you very much
-
Definitely agree, PSS is the way to go here. Please post back with what you find.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
-
I will, Thank you
-
Hello, this is my info about my server,but how can I see if there SP2 for SQL 2005
Microsoft SQL Server Management Studio9.00.4035.00
Microsoft Analysis Services Client Tools2005.090.4035.00
Microsoft Data Access Components (MDAC)2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML2.6 3.0 5.0 6.0
Microsoft Internet Explorer8.0.6001.18702
Microsoft .NET Framework2.0.50727.42
Operating System5.2.3790
-
Your SQL Server 2005 is at SP3 according to the long version numer
See the link below, it lists all version numbers:
-
Thank you, how can I check how much RAM I have? I was told we have have 4GB, The OS is Win 2K3 ENTERPRISE. I wanted it to see for myself.
-
Krasavita (2/23/2011)
Hello, this is my info about my server,but how can I see if there SP2 for SQL 2005Microsoft SQL Server Management Studio9.00.4035.00
Microsoft Analysis Services Client Tools2005.090.4035.00
Microsoft Data Access Components (MDAC)2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML2.6 3.0 5.0 6.0
Microsoft Internet Explorer8.0.6001.18702
Microsoft .NET Framework2.0.50727.42
Operating System5.2.3790
How did you pull this?
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
-
Most probably from the Help --> About screen.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply