Hi
SQL Service went down on production server. Below is the only error message on event logs. There is no more information in the sql server logs.MSSQLSERVER service terminated unexpectedly.It has done this 1 Time(s).
Any advise?
Thanks
January 16, 2017 at 12:27 pm
Hi
SQL Service went down on production server. Below is the only error message on event logs. There is no more information in the sql server logs.MSSQLSERVER service terminated unexpectedly.It has done this 1 Time(s).
Any advise?
Thanks
January 16, 2017 at 12:38 pm
look in the windows event logs;
you might see something like the network guys installing patches, which required a reboot;
look deeper into the sql server log, specifically at the last entries in Atchive #1
there';s typically a lot of detail in there, it's simply not possible for a single line in the error log to represent a downing of the service or server.
for example, i see something like this:
SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
Service Broker manager has shut down.
.NET Framework runtime has been stopped.
SQL Server shutdown has been initiated
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvcMySQLServer.MyDomain.org ] for the SQL Server
Lowell
January 17, 2017 at 9:39 pm
This was removed by the editor as SPAM
January 17, 2017 at 10:33 pm
i have found similar thread, hope it help: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/a6dd2c4b-482f-45be-a3e8-f40af98618b9/the-mssqlserver-service-terminated-unexpectedly
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply