| Details | |
| Product: | SQL Server |
| Event ID: | 8443 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | SB_DIALOG_WO_CONV_GROUP |
| Message: | The conversation with ID ‘%.*ls’ and initiator: %d references a missing conversation group ‘%.*ls’. Run DBCC CHECKDB to analyze and repair the database. |
| Explanation | |
|
The metadata layer returned NULL for the conversation group. The database has been corrupted in some way. One possible source of corruption is a disk error. |
|
| User Action | |
|
Run DBCC CHECKDB in repair mode to bring the database back into a consistent state. It may delete messages if necessary to restore consistency. Investigate system error logs to see if this error was caused by another failure in the system. |
|
Tag: SQL Server 9.0
System table pre-checks: Object ID O_ID has chain linkage mismatch. P_ID1->next = P_ID2, but P_ID2->prev = P_ID3. Check statement terminated due to unrepairable error.
| Details | |
| Product: | SQL Server |
| Event ID: | 7987 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_PRE_CHECKS_CHAIN_LINKAGE_MISMATCH |
| Message: | System table pre-checks: Object ID O_ID has chain linkage mismatch. P_ID1->next = P_ID2, but P_ID2->prev = P_ID3. Check statement terminated due to unrepairable error. |
| Explanation | |
|
The first phase of a DBCC CHECKDB is to do primitive checks on the data pages of critical system tables. If any errors are found, they cannot be repaired; therefore, the DBCC CHECKDB terminates immediately. The next page pointer of page P_ID1 points to page P_ID2; however, the previous page pointer of page P_ID2 points to page P_ID3 but not back to page P_ID1, as it should. |
|
| User Action | |
| Look for Hardware Failure
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs. If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system. Restore from Backup If the problem is not hardware related and a known clean backup is available, restore the database from the backup. Run DBCC CHECKDB Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Service and Support (CSS). |
|
Related:
System table pre-checks: Object ID O_ID has cross-object chain linkage. Page P_ID1 points to P_ID2 in alloc unit ID A_ID1 (should be A_ID2). Check statement terminated due to unrepairable error.
| Details | |
| Product: | SQL Server |
| Event ID: | 7986 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_PRE_CHECKS_CROSS_OBJECT_LINKAGE |
| Message: | System table pre-checks: Object ID O_ID has cross-object chain linkage. Page P_ID1 points to P_ID2 in alloc unit ID A_ID1 (should be A_ID2). Check statement terminated due to unrepairable error. |
| Explanation | |
|
The first phase of a DBCC CHECKDB is to do primitive checks on the data pages of critical system tables. If any errors are found, they cannot be repaired; therefore, the DBCC CHECKDB terminates immediately. The next page pointer of page P_ID1 in the data level of the specified object points to a page, P_ID2, in a different object. |
|
| User Action | |
| Look for Hardware Failure
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs. If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system. Restore from Backup If the problem is not hardware related and a known clean backup is available, restore the database from the backup. Run DBCC CHECKDB Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS). |
|
Related:
System table pre-checks: Object ID O_ID. Page P_ID has unexpected page type PAGETYPE. Check statement terminated due to unrepairable error.
| Details | |
| Product: | SQL Server |
| Event ID: | 7984 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_PRE_CHECKS_BAD_PAGE_TYPE |
| Message: | System table pre-checks: Object ID O_ID. Page P_ID has unexpected page type PAGETYPE. Check statement terminated due to unrepairable error. |
| Explanation | |
|
A page with a type other than DATA_PAGE was found in the data level of the specified object. This error is raised during the first phase of the DBCC CHECKDB command checks. During this phase, DBCC CHECKDB performs primitive checks on the data pages of critical system base tables. Note: If any errors are found in the system tables, the errors cannot be repaired; therefore, the DBCC CHECKDB command ends immediately. |
|
| User Action | |
| Look for Hardware Failure
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs. If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system. Restore from Backup If the problem is not hardware related and a known clean backup is available, restore the database from the backup. Run DBCC CHECKDB Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Service and Support (CSS). |
|
Related:
Table error: Filestream directory exists for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID, but that column is not a Filestream column.
| Details | |
| Product: | SQL Server |
| Event ID: | 7936 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_FS_ORPHANED_COLUMN_DIRECTORY |
| Message: | Table error: Filestream directory exists for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID, but that column is not a Filestream column. |
| Explanation | |
|
During DBCC CHECKDB, a Filestream directory was found for the specified column C_ID; however, the data type of the column is not Filestream. |
|
| User Action | |
| Look for Hardware Failure
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs. If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system. Restore from Backup If the problem is not hardware related and a known clean backup is available, restore the database from the backup. Run DBCC CHECKDB Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS). |
|
Related:
Table error: Filestream directory exists for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID, but that column does not exist in the partition.
| Details | |
| Product: | SQL Server |
| Event ID: | 7935 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_FS_MISSING_COLUMN |
| Message: | Table error: Filestream directory exists for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID, but that column does not exist in the partition. |
| Explanation | |
|
During DBCC CHECKDB, a Filestream directory was found for the specified column; however, the column was not found in the corresponding metadata of the partition. |
|
| User Action | |
| Look for Hardware Failure
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs. If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system. Restore from Backup If the problem is not hardware related and a known clean backup is available, restore the database from the backup. Run DBCC CHECKDB Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS). |
|
Related:
Table error: Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID was not found.
| Details | |
| Product: | SQL Server |
| Event ID: | 7934 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_FS_MISSING_ROWSET_DIRECTORY |
| Message: | Table error: Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID was not found. |
| Explanation | |
|
During DBCC CHECKDB, a partition was found; however, its corresponding Filestream rowset directory in the Filestream dataspace was not found. |
|
| User Action | |
| Look for Hardware Failure
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs. If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system. Restore from Backup If the problem is not hardware related and a known clean backup is available, restore the database from the backup. Run DBCC CHECKDB Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS). |
|
Related:
Table error: Filestream directory for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID was not found.
| Details | |
| Product: | SQL Server |
| Event ID: | 7937 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_FS_MISSING_COLUMN_DIRECTORY |
| Message: | Table error: Filestream directory for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID was not found. |
| Explanation | |
|
The specified column exists in a partition; however, its corresponding Filestream directory was not found in the Filestream dataspace. |
|
| User Action | |
| Look for Hardware Failure
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs. If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system. Restore from Backup If the problem is not hardware related and a known clean backup is available, restore the database from the backup. Run DBCC CHECKDB Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS). |
|
Related:
Table error: Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID is in filegroup FG_ID1, but should be in filegroup FG_ID2.
| Details | |
| Product: | SQL Server |
| Event ID: | 7932 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_FS_ROWSET_IN_WRONG_FILEGROUP |
| Message: | Table error: Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID is in filegroup FG_ID1, but should be in filegroup FG_ID2. |
| Explanation | |
|
During DBCC CHECKDB, the Filestream storage for an object was detected in the wrong filegroup. This could be a corruption in the metadata of the object. |
|
| User Action | |
| Look for Hardware Failure
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs. If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system. Restore from Backup If the problem is not hardware related and a known clean backup is available, restore the database from the backup. Run DBCC CHECKDB Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS). |
|
Related:
Repair: Deleted record for object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE), on page P_ID, slot S_ID. Indexes will be rebuilt.
| Details | |
| Product: | SQL Server |
| Event ID: | 7916 |
| Source: | MSSQLServer |
| Version: | 9.0 |
| Component: | SQLEngine |
| Symbolic Name: | DBCC2_REPAIR_RECORD_DELETED |
| Message: | Repair: Deleted record for object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE), on page P_ID, slot S_ID. Indexes will be rebuilt. |
| Explanation | |
|
This is an information messages sent by REPAIR that indicates the specified record was deleted from the page. |
|
| User Action | |
|
None |
|