Although the MSSQLServer service does not stop, there is a “The MSSQLServer service terminated unexpectedly” Critical Error severity alert in the Microsoft Operations Manager 2005 Operator Console
Symptoms
Although the MSSQLServer service does not stop, the Microsoft Operations Manager (MOM) 2005 Operator Console contains a Critical Error severity alert that is similar to the following alert:
Name: The MSSQLServer service terminated unexpectedlySeverity: Critical ErrorResolution State: NewDomain: WORKGROUPComputer: ComputerNameTime of First Event: TimeTime of Last Event: TimeAlert latency: 1 secProblem State: InvestigateRepeat Count: 3Age:Source: MSSQLSERVERAlert Id: 390da845-d0c7-4570-b895-cb265d13addaRule (enabled): Microsoft SQL Server\SQL Server 2000\SQL Server 2000 Event Collection\SQL Server General\The MSSQLServer service terminated unexpectedlyDescription: SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Resolution
This issue occurs when the following conditions are true: You enable the The MSSQLServer service terminated unexpectedly event rule. This event rule has the following criteria in the MOM 2005 Administrator Console: The Event Number event property matches the following code:
regex ^(17052|17055)$The Source Name event property matches the following code:
wildcard MSSQL*The Description event property matches the following code:
substring Error: 0, Severity: 19, State: 0You receive an error message that has a severity level 19 in Microsoft SQL Server 2000 that is similar to the following error message:
ODBC: Msg 0. Level 19, State 1SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.Connection Broken
