Sql server 2008 R2 Automatically stopped

Question

My SQL Server 2008 R2 instance

06/24/2011 13:48:24,Server,Unknown,The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ XXXXXXXXXXXXXXX ] for the SQL Server service.

06/24/2011 13:48:24,Server,Unknown,The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ XXXXXXXXXXXXXXX ] for the SQL Server service.

06/24/2011 13:48:23,spid6s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

06/24/2011 13:48:23,spid6s,Unknown,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.

06/24/2011 13:48:18,spid13s,Unknown,Service Broker manager has shut down.

06/24/2011 13:48:12,spid113,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQL2008R2'.

06/24/2011 13:48:12,spid113,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.

06/24/2011 13:48:12,spid113,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQL2008R2'.

06/24/2011 13:48:12,spid113,Unknown,Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.

06/24/2011 13:48:12,spid113,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQL2008R2'.

06/24/2011 13:48:12,spid113,Unknown,Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

Please help me to find a reason

Akkiraju Ivaturi · Answer

Check the windows logs. If it is not working then try to restore the sql server program using restore points.

Robert Nimstrom · Answer

I have the same problem 2012-09-04 00:15:32 spid5s 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. 2012-09-04 00:15:29 spid59 Error: 18056 Severity: 20 State: 23. 2012-09-04 00:15:29 spid59 The client was unable to reuse a session with SPID 59 which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

Suthish Nair · Answer

Do you have multiple sql server instances on your system. This must having conflict when using the default port. Stop the other instance reboot the system and try..