The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

Details
Product: SQL Server
Event ID: 823
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: B_HARDERR
Message: The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
   
Explanation

A Windows read or write request has failed. The error code that is returned by Windows and the corresponding text are inserted into the message. In the read case, SQL Server will have already retried the read request four times. This error is often the result of a hardware error, but may be caused by the device driver. For more information about error 823, see
http://support.microsoft.com/kb/828339http://support.microsoft.com/kb/828339
. For more information about I/O errors, see
Microsoft SQL Server I/O Basics, Chapter 2http://go.microsoft.com/fwlink/?LinkId=69370
.

   
User Action

Check for additional information in the system event log. Contact the hardware manufacturer or Microsoft Customer Services and Support to determine the cause and corrective action. After the hardware error is fixed, restore all databases and run DBCC CHECKDB.

Related:

The %1 service terminated with service-specific error %2.

Details
Product: Windows Operating System
Event ID: 7024
Source: Service Control Manager
Version: 5.2
Symbolic Name: EVENT_SERVICE_EXIT_FAILED_SPECIFIC
Message: The %1 service terminated with service-specific error %2.
   
Explanation

The specified service stopped unexpectedly with the error indicated in the message. Windows does not recognize the service’s error code.

   
User Action

To display the service-specific error code in the Service_Exit_Code field, at the command line, type
sc query
service nameThe information displayed might help you troubleshoot why the error occurred.

Related: