August 16, 2019 at 1:19 pm
Recently been asked to look at why ASQL instance will nto start. this CLuster has not been built to best practice and is a 2 node cluster. it has 13 instances across it. AN instance was failed over yesterday and as such all instances started bar this one and the log is bringing back an issue that is stating.
2019-08-16 14:12:55.21 spid7s Error: 17311, Severity: 16, State: 1.
2019-08-16 14:12:55.21 spid7s SQL Server is terminating because of fatal exception c06d007e. 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).
2019-08-16 14:12:55.21 spid7s SQL Server shutdown has been initiated
I can't see anything else in the log as to why this is happening.
Anyone experienced this?
August 17, 2019 at 2:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
August 18, 2019 at 5:52 am
Recently been asked to look at why ASQL instance will nto start. this CLuster has not been built to best practice and is a 2 node cluster. it has 13 instances across it. AN instance was failed over yesterday and as such all instances started bar this one and the log is bringing back an issue that is stating.
2019-08-16 14:12:55.21 spid7s Error: 17311, Severity: 16, State: 1.
2019-08-16 14:12:55.21 spid7s SQL Server is terminating because of fatal exception c06d007e. 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).
2019-08-16 14:12:55.21 spid7s SQL Server shutdown has been initiated
I can't see anything else in the log as to why this is happening.
Anyone experienced this?
Call MS Customer support and log a case with them.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply