SQL Server is terminating because of fatal excepti

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

New to SQL Server Administration

SQL Server is terminating because of fatal excepti

Author

Topic

valerie
Starting Member

1 Post

Posted - 2011-02-22 : 13:31:33

Why I am getting this?

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).
This is the rest of the error log message:

Login succeeded for user 'US-CRS\svc_MOSSSearch2'. 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 'US-CRS\svc_MOSSSearch2'. 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 'US-CRS\svc_MOSSSearch2'. 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 'US-CRS\svc_MOSSSearch2'. 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]

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-02-22 : 15:10:32

Show us the output of SELECT @@VERSION.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

Jahanzaib
Posting Yak Master

115 Posts

Posted - 2011-05-06 : 07:06:26

Which Version of OS and SQL Server you are using and Total Memory and allocated memory for SQL Server

Have you applied update Service Packs and Cummulative Updates,if not then apply latest CU or service pack

Regards,

Syed Jahanzaib Bin Hassan
MCTS,MCITP,OCA,OCP,OCE,SCJP,IBMCDBA

My Blog
www.aureus-salah.com

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-05-06 : 09:57:36

Honestly, the best thing probably will be to call MS customer support and log a case. They have tools to read stack dumps, we don't.

--
Gail Shaw
SQL Server MVP

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2011-05-06 : 10:36:55

I'd start with this
Not enough storage is available to process this command

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources