Production SQL server down!

Someone attempted to change the partition layout of our SQL cluster, then we
recieved an error:
"Could not start the MSSQLSERVER service on local computer. The service did
not return an error. This could be an internal Windows error or an internal
service error. . . ."
in event log, we have two repetitive errors (application), and errors in
system log:
Application:
Event ID #17052
Error: 17826, Severity: 18, State: 1
Could not set up Net-Library 'SSNETLIB'.
and
Event ID#17055
17120 :
SQL Server could not spawn FRunCM thread.
System:
Event ID#1069
Cluster resource 'SQL Server' failed.
Any ideas? I've been "googling" all morning
If your production SQL Server is down then I would suggest opening a case with Microsoft Product Support Services (PSS).
Newsgroups doesn't work well for critical situations that needs to be resolved asap.
The error messages that you mentioned could have many causes and a thourough diagnoses is required to find root
cause. One has to review the SQL Server Errorlogs, NT Event Logs, Cluster logs for a start. One may also need to review
the Cluster hive and other cluster related registry keys.
Here are some ideas:
What error messages do you see in SQL Server Errorlog?
Along with the errors that you mentioned are you also getting the following message
Encryption requested but no valid certificate was found. SQL Server terminating
Has somebody turned on the Force Protocol Encryption option in Server Network Utility ?
BUG: Turning On the 'Force Protocol Encryption' Option Is Irreversible If There Is No Certificate
http://support.microsoft.com/?id=319349
Since SQL Server is not coming online, you will not be able to open Server Network Utility. I will check the following registry
key :
For default instance
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SuperSocketNetLib
For named instance
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer
\SuperSocketNetLib
See if it has the 'Encrypt' key. It will be present and set to 1 if Force Protocol Encryption is enabled. If it does not exist, it will
indicate that the encryption was never set.
If encryption is not set then the reason may be something different.
One more thing that comes to miind now is to check the Parameters key in the CLUSTER hive in the registry.
-- Locate the SQL Server Resource in the Cluster Hive under the Resources Key. Then drill down to the Parameters key
under the SQL Server Resource.
We should see the following two values under the Parameters Key.
(HKLM\Cluster\Resources\{GUID for Resource}\Parameters\)
Default Instance
Name: InstanceName Type: Reg_SZ Data: MSSQLSERVER
Name: VirtualServerName Type: Reg_SZ Data: Virtual SQL Server Name
Named Instance
Name: InstanceName Type: Reg_SZ Data: Instance Name of the SQL Server
Name: VirtualServerName Type: Reg_SZ Data: Virtual SQL Server Name
If these are missing then add them and see if you can bring SQL Server resource online. If you have another (working)
cluster, you may want to see the values under Parameter Key first and then make the changes on the problem cluster.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security
Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against
viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Another point to consider:
If it turns out that the Parameters key is empty (and based on the
description of what happened, I believe this is it) then verirfy that the
following key exists:
HKLM\Cluster\Resources\{GUID for Resource}\RegSync.
If not, then this key will have to be recreated and the checkpoint files
for SQL Server may need to be recreated. You will probably want to open a
case with Microsoft Product Support Services (PSS) to help recreate the
checkpoint files.
Rand
This posting is provided "as is" with no warranties and confers no rights.