Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d.

Details
Product: SQL Server
Event ID: 605
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: WRONGPAGE
Message: Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d.
   
Explanation

This error generally signifies page or allocation corruption in the specified database. SQL Server detects corruption when reading pages belonging to a table either by following the page linkages or by using the Index Allocation Map (IAM). All pages allocated to a table must belong to one of the allocation units associated with the table. If the allocation unit ID contained in the page header does not match an allocation unit ID associated with the table, this exception is raised. The first allocation unit ID listed in the error message is the ID present in the page header, the second allocation unit value is the ID associated with the table.

Data Corruption Errors

A severity level of 21 indicates potential data corruption. Possible causes are a damaged page chain, a corrupt IAM, or an invalid entry in the sys.objects catalog view for that object. These errors are often caused by hardware or disk device driver failure.

Transient Errors

A severity level of 12 indicates a potential transient error; that is, it occurs in the cache and does not indicate damage to data on disk. Transient 605 errors can be caused by the following conditions:

  • The operating system prematurely notifies SQL Server that an I/O operation has completed; the error message is displayed even though no actual data corruption exists.

  • Running a query with the Optimizer hint NOLOCK or setting the transaction isolation level to READ UNCOMMITTED. When a query that is using NOLOCK or READ UNCOMMITTED tries to read data that is being moved or changed by another user, a 605 error occurs. To verify that it is a transient 605 error, rerun the query later. For more information, see this
    KB articlehttp://support.microsoft.com/kb/235880/en-us
    .

In general, if the error occurs during data access but subsequent DBCC CHECKDB operations complete without error, the 605 error was probably transient.

   
User Action
  1. Identify the tables associated with the allocation units specified in the message by running the following query. Replace with the allocation units specified in the error message.

    USE ;
    GO
    SELECT au.allocation_unit_id, OBJECT_NAME(p.object_id) AS table_name, fg.name AS filegroup_name,
    au.type_desc AS allocation_type, au.data_pages, partition_number
    FROM sys.allocation_units AS au
    JOIN sys.partitions AS p ON au.container_id = p.partition_id
    JOIN sys.filegroups AS fg ON fg.data_space_id = au.data_space_id
    WHERE au.allocation_unit_id = OR au.allocation_unit_id =
    ORDER BY au.allocation_unit_id;
    GO

  2. Execute DBCC CHECKTABLE without a REPAIR clause on the table associated with the second allocation unit ID specified in the error message.

  3. Execute DBCC CHECKDB without a REPAIR clause as soon as possible to determine the full extent of the corruption in the entire database.

  4. Check the error log for other errors that often accompany a 605 error and examine the Windows Event Log for any system or hardware related issues. Fix any hardware-related problems that are contained in the logs.

  5. If the 605 error is not transient, the problem is severe and must be corrected by performing one of the following tasks:

    1. If the problem is not hardware related and a known clean backup is available, restore the database from the backup. You can leverage the page restore backup feature to restore just the damaged pages.

    2. Run DBCC CHECKDB with the REPAIR clause recommended by the DBCC CHECKDB operation performed in step 2 to repair the corruption.

    Caution:

    If you are not sure what effect DBCC CHECKDB with a REPAIR clause has on your data, contact your primary support provider before running this statement.

    1. If running DBCC CHECKDB with one of the REPAIR clauses does not correct the problem, contact your primary support provider. Have the output from DBCC CHECKDB available for review.

Related:

An inconsistency was detected during an internal operation. Please contact technical support. Reference number %ld.

Details
Product: SQL Server
Event ID: 5243
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Message: An inconsistency was detected during an internal operation. Please contact technical support. Reference number %ld.
   
Explanation

SQL Server detected a structural inconsistency in an in-memory storage engine structure.

   
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 BackupIf the problem is not hardware related and a known clean backup is available, restore the database from the backup.Run DBCC CHECKDBIf no clean backup is available, run DBCC CHECKDB without a REPAIR clause to determine the extent of the corruption. DBCC CHECKDB will recommend a REPAIR clause to use. Then, run DBCC CHECKDB with the appropriate REPAIR clause to repair the corruption.Caution:If you are not sure what effect DBCC CHECKDB with a REPAIR clause has on your data, contact your primary support provider before running this statement.If running DBCC CHECKDB with one of the REPAIR clauses does not correct the problem, contact your primary support provider.

Related:

The LSN %S_LSN passed to log scan in database ‘%.*ls’ is invalid.

Details
Product: SQL Server
Event ID: 9003
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: The LSN %S_LSN passed to log scan in database ‘%.*ls’ is invalid.
   
Explanation
If you see this message during startup when the SQL Server process tries to recover the database or as a result of an ATTACH statement, the log file for the database is corrupted. If you see the message during a restore process, the backup file is corrupted. If you see this message during a replication process, the replication metadata may be incorrect.
   
User Action
If you see the error during a restore process, check the integrity of the backup file. If possible, create a new backup in a new location and retry the restore with the new backup file.

If you see this error during startup or when you try to attach a database:

HARDWARE FAILURE

Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware-related problems.

If you have persistent data inconsistency problems, try to swap out different hardware components to isolate the problem. Check that your system does not have write caching enabled on the disk controller. If you suspect this to be the case, contact your hardware vendor.

Finally, you might find it beneficial to switch to a completely new hardware system, including 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.

DBCC CHECKDB

If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.

Related:

%1 (%2) %3An attempt to read from the file “%4” at offset %5 for %6 bytes failed after %10 seconds with system error %8: “%9”. The read operation will fail with error %7. If this error persists then the file may be damaged and may need to be restored from a previous backup.

Details
Product: Exchange
Event ID: 481
Source: ESE
Version: 8.0
Symbolic Name: OSFILE_READ_ERROR_ID
Message: %1 (%2) %3An attempt to read from the file “%4” at offset %5 for %6 bytes failed after %10 seconds with system error %8: “%9”. The read operation will fail with error %7. If this error persists then the file may be damaged and may need to be restored from a previous backup.
   
Explanation

This Warning event indicates that an unexpected error occurred while reading the file specified in the message. ESE Event ID 481 refers to a failed read attempt from the database. For comparison, ESE Event ID 482 refers to a failed write operation to a log file or a database.

The cause depends on the error number in the Description section of the event. The most common error codes for event 481 are as follows:

  • Error -1022 = 0xfffffc02 = 4294966274 = Jet_errDiskIO = Disk I/O error. The -1022 error is a generic error that appears whenever a disk I/O problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. Check the System log for I/O or drive errors near the time of the 490 event. This issue may occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure.

  • Error -1811 = 0xfffff8ed = Jet_errFileNotFound = File not found. The database may be missing or there may be other causes for this error. Another reason for error -1811 could be that the Exchange database and log files may have been put on network storage, which is not supported. Also, the checkpoint file may be corrupt, or the log drive itself may have failed. Exchange will disconnect from the storage group due to an inability to locate the database files. Typically, this is due to a hardware problem.

  • Error -1011 = 0xfffffc0d = Jet_errOutOfMemory = Out of Memory. This error indicates that there is no more available memory and the read operation has failed. Other ESE events with out-of-memory errors in the Description section for reading the header of a database, recovery/restore, and starting a storage group are often seen in the application event log at the same time. Review these events for further information.

  • Error -1003 = 0xfffffc15 = Jet_errInvalidParameter = Incorrect API parameter. This error generally means that the file size of the database is not a multiple of 4,096 bytes.

   
User Action

To resolve this warning, do one or more of the following:

  • Review the disk and file that you are trying to read. Check the integrity of the file system. Check the memory usage. Check the system portion of the event log for related entries. Review and change the access permissions properties and then note the disk space available. Check the file size of the database in bytes.

  • For error -1022, check to ensure that the drive for the Exchange store files is accessible and that the path for the Exchange store files is specified correctly. If it is, run chkdsk /f /r. If chkdsk does not resolve the issue, examine the permissions on the C:\Program Files\Microsoft\Exchange Server folder, where C:\ is the directory to which you installed Exchange 2007. Ensure that System has full control of the Exchange Server folder and all subfolders on each partition that contain Exchange data. If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange server. Check the System log for I/O or drive errors near the time of the 413 event.

  • For error -1811, ensure that the antivirus software is not running against the Exchange store, the SRS database directories. Make sure that you have properly configured your antivirus software. For more information, see the Microsoft Knowledge Base article 328841, Exchange and Antivirus Software.

  • Ensure that the database drive has not run out of space. Ensure that the database file is where it is supposed to be.

  • For error -1011, check the memory usage of the server. Check the settings for the page file. Check for memory-related events in the application event log and in the System log and check the Microsoft Knowledge Base for troubleshooting of the events found. For error -1003, check the size of the database in bytes. It must be a multiple of 4,096 bytes, or 1 page. If it is not, contact Microsoft Product Support Services.

  • For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

LDM – Internal dmboot Service error

Details
Product: Windows Operating System
Event ID: 5
Source: dmboot
Version: 5.2.3790.1830
Message: LDM – Internal dmboot Service error
   
Explanation

This event indicates that the Logical Disk Manager service detected an internal error during the startup process of the server.

Cause

Possible causes include:

  • A hardware failure that prevents communication with a disk (for example, a loose cable, a loose disk controller card, or a cable failure).
  • Unexpected removal of a disk.
  • Uncorrectable bad sectors on a disk.
  • A software error.
   
User Action

Do one or more of the following:

  • Check the status of your hardware for any failures (for example, a disk, controller card, or cable failure).
  • Check Event Viewer for additional events from lower-level storage drivers that might indicate the cause of the failure.
  • Restart the system.
  • Contact Microsoft Customer Service and Support.

Related: