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.
| Author |
Topic |
|
AnitaDBA2010
Starting Member
18 Posts |
 Posted - 2010-12-28 : 16:39:55
|
| Hi All-SQL Server in stopped state. Tried to restart this morning resulted in below errorEventViewer LogsSQL Server 2005 process terminates automatically with the error "SQL Server is terminating because of fatal exception c0000005. 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)." Error Log DumpError: 17311, Severity: 16, State: 1.2010-12-28 13:15:59.54 Server SQL Server is terminating because of fatal exception c0000005. 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).Any ideas why sql server is not restarting? Your help is much appreciated. It was working fine a week ago :(Verified and made sure service account to start sql server has access to all sql directories but still same error :(ThanksAnitaAnita |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
AnitaDBA2010
Starting Member
18 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
AnitaDBA2010
Starting Member
18 Posts |
Posted - 2010-12-30 : 12:46:25
|
Thanks TaraBelow is what we found in the SQLDUMP error log file 00000000`055feb10 00000000`028e063a sqlservr!NodeManager::LoadNodeConfiguration+0x17e [e:\sql10_main_t\sql\common\dk\sos\src\os.cpp @ 988]Sqlservr!NodeManager is determining memory and CPU node configurationThere has been some change for memory and CPU configurations.And ERRORLOG shows SQL Server has been terminated before setting memory utilizationThanksAnitaquote:
Originally posted by tkizer
Interesting. You should open a case with MS as it sounds like you've encountered a SQL Server bug. Only they can fix it.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog
Anita |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-12-30 : 16:43:14
|
| Call customer support and log a case with them. They have the tools to interpret stack dumps, we don't.--Gail ShawSQL Server MVP |
|
|
|
|
|
|
Error17311 SQLServer terminating Access Violation