SQL 2005 Express will not start

Question

Service just would not start after a reboot I have approximately 30 clients this has happened to basically out of the blue and they started happening approximately 6/17/2014. The SQL log and event log errrors are below. Uninstall reinstall only fails, switching
to local service account throws WMI Provider Error, Can't find object or property" [0x80092004]. The common issue seems to be a malware infection of Search Protect. Please advise before this gets worse. Thank you.
SQL 2005 wont start error logs
FallBack certificate initialization failed with error code: 1.  17190
TDSSNIClient initialization failed with error 0x80092004, status code 0x80.  17182
TDSSNIClient initialization failed with error 0x80092004, status code 0x1.  17182
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.  17826
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.  17120
The SQL Server (VSDOTNET) service terminated with service-specific error %%-2146885628.  7024
FallBack certificate initialization failed with error code: 1.  17190
INFO-Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.  26017
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.  17826
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. 17120
WMI Provider Error
"Can't find object or property" [0x80092004]
SQL Start up log
2014-06-26 09:18:54.83 Server      Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
    Dec 10 2010 10:56:29
    Copyright (c) 1988-2005 Microsoft Corporation
    Express Edition on Windows NT 6.1 (Build 7601: Service Pack 1)
2014-06-26 09:18:54.83 Server      (c) 2005 Microsoft Corporation.
2014-06-26 09:18:54.83 Server      All rights reserved.
2014-06-26 09:18:54.83 Server      Server process ID is 2716.
2014-06-26 09:18:54.83 Server      Authentication mode is MIXED.
2014-06-26 09:18:54.83 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2014-06-26 09:18:54.83 Server      This instance of SQL Server last reported using a process ID of 4936 at 6/26/2014 9:13:53 AM (local) 6/26/2014 2:13:53 PM (UTC). This is an informational message only; no user action is required.
2014-06-26 09:18:54.83 Server      Registry startup parameters:
2014-06-26 09:18:54.83 Server           -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2014-06-26 09:18:54.83 Server           -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2014-06-26 09:18:54.83 Server           -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2014-06-26 09:18:54.84 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-06-26 09:18:54.84 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2014-06-26 09:18:54.94 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.
2014-06-26 09:18:54.95 Server      Database mirroring has been enabled on this instance of SQL Server.
2014-06-26 09:18:54.96 spid4s      Starting up database 'master'.
2014-06-26 09:18:55.11 spid4s      SQL Trace ID 1 was started by login "sa".
2014-06-26 09:18:55.13 spid4s      Starting up database 'mssqlsystemresource'.
2014-06-26 09:18:55.15 spid4s      The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2014-06-26 09:18:55.32 Server      Error: 17190, Severity: 16, State: 1.
2014-06-26 09:18:55.32 Server      FallBack certificate initialization failed with error code: 1.
2014-06-26 09:18:55.32 spid4s      Server name is '2UA1371VFY\VSDOTNET'. This is an informational message only. No user action is required.
2014-06-26 09:18:55.32 spid8s      Starting up database 'model'.
2014-06-26 09:18:55.32 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-06-26 09:18:55.32 spid4s      Starting up database 'msdb'.
2014-06-26 09:18:55.32 Server      Error: 17182, Severity: 16, State: 1.
2014-06-26 09:18:55.32 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
2014-06-26 09:18:55.32 Server      Error: 17182, Severity: 16, State: 1.
2014-06-26 09:18:55.32 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1.
2014-06-26 09:18:55.32 Server      Error: 17826, Severity: 18, State: 3.
2014-06-26 09:18:55.32 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.
2014-06-26 09:18:55.33 Server      Error: 17120, Severity: 16, State: 1.
2014-06-26 09:18:55.33 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.
James Ball

Answer 1

This is what I found by someone else;
I know it's probably too late to help with the original poster, but we had this same issue and nothing we tried resolved the problem. Finally, we opened a technical incident with Microsoft and this is the solution that we were provided:
Take backup of below registry key.
HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid This key should ideally have the GUID of the machine without curly braces, so {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} becomes xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Then delete the braces.
Try to reboot and start the SQL service . If service don’t start then Uninstall and reinstall SQL.
The above solution worked on two separate machines exhibiting this problem.
Monday, June 30, 2014 3:03 PM
jawg
(Partner)
10 Point
James Ball