| Event Id | 3413 |
| Source | MSSQLServer |
| Description | Database ID %d. Could not mark database as suspect. Getnext NC scan on sysdatabases.dbid failed. |
| Event Information | CAUSE: The SQL Server recovery process tried to turn on the suspect flag for the specified database, but it could not find the appropriate row in sysdatabases or could not update the database information in memory. The reason the database needs to be marked suspect should be indicated by other messages in the SQL Server error log or the Event Viewer. A database can become suspect for several reasons. Possible causes include denial of access to a database resource by the operating system, and the unavailability or corruption of one or more database files. RESOLUTION: Review the SQL Server error log and the event logs for messages indicating the reason the database needed to be marked suspect. Then resolve all data integrity issues with the database. |
| Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 3413 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.