Log Name: ApplicationSource: MSSQL$<SQL Cluster group name>Event ID: 17141Task Category: (2)Level: ErrorKeywords: ClassicDescription:Could not register Service Control Handler. Operating system error = 2310 (This shared resource does not exist.).
Log Name: ApplicationSource: Application ErrorEvent ID: 1000Task Category: Application Crashing EventsLevel: ErrorKeywords: ClassicDescription:Faulting application name: svchost.exe_<serviceName>, version: <version>, time stamp: <time stamp>Faulting module name: <module name>, version: <version#>, time stamp: <time stamp>Exception code: <code>Fault offset: <number>Faulting process id: <PID>Faulting application start time: <time stamp>Faulting application path: C:\Windows\system32\svchost.exeFaulting module path: <module full path>Report Id: <GUID>Faulting package full name: Faulting package-relative application ID:
This problem occurs because LanManServer crashed previously and then restarted.
If the LanManServer service exits without a proper shutdown, the kernel driver information is not cleaned out. When LanManServer service automatically restarts later, the service uses the kernel information to skip registering the server NetBIOS name to an internal server name list. In this situation, when the SQL Server cluster tries unsuccessfully to come online, it calls the SetServiceBits API and generates error code 2310.
To fix this problem, restart the LanManServer service manually.
By using a graceful service shutdown and restart, LanManServer is initialized by using correct information. The SQL Server cluster group can then be brought online successfully.
Check for shared services
sc config ProfSvc type=own
sc config profsvc type=share
Create crash dumps automatically
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
To help determine the cause of a service crash, you can create a svchost.exe registry key to generate crash dumps for cause analysis. Analyzing dumps requires debugging skill. You can use Debugging Tools for Windows (windbg) or Debug Diagnostic Tool to analyze the dumps. For Windows service crash dumps, contact Microsoft Support for additional help.
To create and set a registry key to generate crash dumps, follow these steps:
- In Registry Editor, locate the following subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps
- Under this subkey, create the following key:
- Under the new key, create the following values:
- DumpFolder Type: REG_EXPAND_SZ
Value: <path_of_stored_dumps> (for example, "c:\SvchostCrashDumps")
Description: Specifies the location in which you want to save the dumps.
- DumpCount Type : REG_DWORD
Description: The number of dumps you want to save. When this number is reached, old dumps are replaced by new ones.
- DumpType Type: REG_DWORD
Description: Dump file. "2" means a full user dump.