Critical Non Impact


MSSQL Failed To Complete Backup Of Database

This alert condition indicates a SQL database failure. Possible causes: low disk space, the contiguous virtual memory is insufficient, or the contiguous virtual memory is too fragmented for the computer to successfully perform a backup.

MSSQL : SQL Server Detected A Logical Consistency Based I/O Error

This alert condition indicates that a SQL-I/O error was detected during read at offset. There can be situations where the Windows API call actually succeeds but the data transferred by the I/O operation might encounter a logical consistency problem. These logical consistency problems are reported through this event.

SQL Log Scan In Database 'model' Is Invalid

This alert condition indicates that the log scan number passed to the log scan in the database is not valid. This error could be the result of data corruption or may indicate that the log file (.ldf) does not match the data file (.mdf).

SQL Could Not Allocate Space For Object

This alert condition indicates that SQL could not allocate space for an object, indicating that the filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth to ON for existing files in the filegroup

SQL Could Not Find Row In Sysindexes For Database

This alert condition indicates that SQL could not find a row in sysindexes for a database.

SQL Insufficient Memory Available

This alert condition indicates that there is insufficient memory available. There was a memory allocation failure while establishing a connection.

SQL Server (BKUPEXEC) Not In Running State

This alert condition indicates that the SQL Server (BKUPEXEC) service is not running.

SQL Server (BKUPEXEC) Not In Running State [Unexpected]

This alert condition indicates that the SQL Server (BKUPEXEC) service terminated unexpectedly.

SQL Server (SQLEXPRESS) Not In Running State

This alert condition indicates that the SQL Server (SQLEXPRESS) service is not running.

SQL Server (SQLEXPRESS) Not In Running State [Unexpected]

This alert condition indicates that the SQL Server (SQLEXPRESS) service terminated unexpectedly.

SQL Server Browser Not In Running State

This alert condition indicates that the SQL Server Browser service is not running.

SQL Server Browser Not In Running State [Unexpected]

This alert condition indicates that the SQL Server Browser service terminated unexpectedly.

SQL Server Integration Services 10 0 Not In Running State

This alert condition indicates that the SQL Server Integration Services 10.0 service is not running.

SQL Server Integration Services 10 0 Not In Running State [Unexpected]

This alert condition indicates that the SQL Server Integration Services 10.0 service terminated unexpectedly.

SQL Server Integration Services 11 0 Not In Running State

SQL Server Integration Services 11.0- Not In Running State

SQL Server Integration Services 11 0 Not In Running State [Unexpected]

SQL Server Integration Services 11.0- Not In Running State [Unexpected]

SQL Server VSS Writer Not In Running State

This alert condition indicates that the SQL Server VSS Writer service is not running.

SQL Server VSS Writer Not In Running State [Unexpected]

This alert condition indicates that the SQL Server VSS Writer service terminated unexpectedly.

SQL The Log File For Database Is Full

This alert condition indicates that the log file for the database is full. The database transaction log should be backed up, to free up log space.

SQLAgent$SBSMONITORING Not In Running State

This alert condition indicates that the SQLAgent$SBSMONITORING service is not running.

SQLAgent$SBSMONITORING Not In Running State [Unexpected]

This alert condition indicates that the SQLAgent$SBSMONITORING service terminated unexpectedly.

SQLAgent$SHAREPOINT Not In Running State

This alert condition indicates that the SQLAgent$SHAREPOINT service is not running.

SQLAgent$SHAREPOINT Not In Running State [Unexpected]

This alert condition indicates that the SQLAgent$SHAREPOINT service terminated unexpectedly.

Last modified April 17, 2020