Quantcast
Channel: SQL Server Database Engine forum
Viewing all articles
Browse latest Browse all 15264

Help - SQL Server 2008 R2 suddenly stopped working! Can't start service

$
0
0

Hello,

I've had SQL Server 2008 R2 running on my Windows 7 Professional 64-bit machine for some time now without problem. I restarted the machine just now, only to find that the SQL Server service hadn't started. To my knowledge, nothing has changed on this machine this afternoon, and it was working fine before.

If I try and start the service manually, I get an error message...

"Windows could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log."

The system log shows the error...

The SQL Server (MSSQLSERVER) service terminated with service-specific error %%-1.

The Application event log shows four error messages from SQL Server (shown in order of when they happened)...

TDSSNIClient initialization failed with error 0xffffffff, status code 0x80. Reason: Unable to initialize SSL support.

TDSSNIClient initialization failed with error 0xffffffff, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors.

Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

The error log in C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log contains the following...

2011-03-03 18:43:56.67 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
    Apr  2 2010 15:48:46
    Copyright (c) Microsoft Corporation
    Web Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

2011-03-03 18:43:56.67 Server      (c) Microsoft Corporation.
2011-03-03 18:43:56.67 Server      All rights reserved.
2011-03-03 18:43:56.67 Server      Server process ID is 3304.
2011-03-03 18:43:56.67 Server      System Manufacturer: 'Dell Inc.', System Model: 'Studio 540'.
2011-03-03 18:43:56.67 Server      Authentication mode is MIXED.
2011-03-03 18:43:56.67 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-03-03 18:43:56.67 Server      This instance of SQL Server last reported using a process ID of 1788 at 03/03/2011 18:42:19 (local) 03/03/2011 18:42:19 (UTC). This is an informational message only; no user action is required.
2011-03-03 18:43:56.67 Server      Registry startup parameters:
     -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
     -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
     -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2011-03-03 18:43:56.69 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-03-03 18:43:56.69 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2011-03-03 18:43:56.72 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2011-03-03 18:43:56.74 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2011-03-03 18:43:56.76 spid7s      Starting up database 'master'.
2011-03-03 18:43:56.84 spid7s      1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2011-03-03 18:43:56.84 spid7s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2011-03-03 18:43:56.84 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
<{39B75A24-0837-4CEC-AFDF-B960027AE07E}>RsFxNso initialized. InstanceId = 00000004
<{50080099-5EC4-4EAF-A2A2-63C3DA97F8EB}>FsAgent is initialized
<{09C4480B-DBA4-49B7-956F-68A8B8B2445D}>FsAgent is up and running
2011-03-03 18:43:56.96 spid7s      FILESTREAM: effective level = 2, configured level = 2, file system access share name = 'MSSQLSERVER'.
2011-03-03 18:43:56.97 spid7s      SQL Trace ID 1 was started by login "sa".
2011-03-03 18:43:56.98 spid7s      Starting up database 'mssqlsystemresource'.
2011-03-03 18:43:56.99 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-03-03 18:43:57.33 spid7s      Server name is 'DAISY'. This is an informational message only. No user action is required.
2011-03-03 18:43:57.44 spid15s     Starting up database 'model'.
2011-03-03 18:43:57.46 Server      A self-generated certificate was successfully loaded for encryption.
2011-03-03 18:43:57.47 Server      Error: 17182, Severity: 16, State: 1.
2011-03-03 18:43:57.47 Server      TDSSNIClient initialization failed with error 0xffffffff, status code 0x80. Reason: Unable to initialize SSL support.
2011-03-03 18:43:57.47 Server      Error: 17182, Severity: 16, State: 1.
2011-03-03 18:43:57.47 Server      TDSSNIClient initialization failed with error 0xffffffff, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors.
2011-03-03 18:43:57.47 Server      Error: 17826, Severity: 18, State: 3.
2011-03-03 18:43:57.47 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2011-03-03 18:43:57.47 Server      Error: 17120, Severity: 16, State: 1.
2011-03-03 18:43:57.47 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Anyone any ideas what could have gone wrong? I'm completely out of my depth here. As I said, I haven't knowingly changed anything this afternoon, and it was working fine earlier. Since I last used it, I did some stuff with Word and Powerpoint, which weren't behaving themselevs, which is why I restarted the machine. Since then I looked at eBay for a bit, then came back to my development work to find SQL Server not working.

Thanks in advance for any help you can give.


If you're really bored, you could read about my experiments with .NET and some of Microsoft's newer technologies athttp://dotnetwhatnot.pixata.co.uk/

Viewing all articles
Browse latest Browse all 15264

Trending Articles