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 (904743)

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 unexpectedly
Severity: Critical Error
Resolution State: New
Domain: WORKGROUP
Computer: ComputerName
Time of First Event: Time
Time of Last Event: Time
Alert latency: 1 sec
Problem State: Investigate
Repeat Count: 3
Age:
Source: MSSQLSERVER
Alert Id: 390da845-d0c7-4570-b895-cb265d13adda
Rule (enabled): Microsoft SQL Server\SQL Server 2000\SQL Server 2000 Event Collection\SQL Server General\The MSSQLServer service terminated unexpectedly
Description: SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

CAUSE

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: 0
```

You 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 1
SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken

MORE INFORMATION

Although the alert may not always indicate that the MSSQLServer service stopped unexpectedly, investigate the issues that trigger this alert. Severity level 19 error messages rarely occur. However, the system administrator or the primary support provider should correct these errors. You should inform the system administrator or the primary support provider every time that a severity level 19 error message occurs. The system administrator or the primary support provider can obtain more information from the SQL Server error log.

REFERENCES

For more information about the error message severity levels in SQL Server 2000, visit the following Microsoft Web site:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_errorformats_0tpv.asp

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 (904743)

SYMPTOMS

CAUSE

STATUS

MORE INFORMATION

REFERENCES