Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 2091098 - Last Review: April 2, 2012 - Revision: 3.0
​Windows System Event Log Errors that indicate possible I/O problems can be associated with database inconsistency or performance problems for SQL Server
You may see the following errors in the Windows System Event Log which can be indicators of system problems that can contribute to SQL Server database inconsistency or performance problems:
Collapse this tableExpand this table
| EventID | Message |
| 9 | The device, <device name>, did not respond within the timeout period |
| 11 | The driver detected a controller error on <device> |
| 15 | The device, <device>, is not ready for access yet |
| 50 | {Delayed Write Failed} Windows was unable to save all the data for the file. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere |
| 51 | An error was detected on device <device path> during a paging operation |
| 54 | An Io Request to the device <device> did not complete or canceled within the specific timeout. This can occur if the device driver does not set a cancel routine for a given IO request packet. |
| 55 | The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume <drive letter> |
| 57 | The system failed to flush data to the transaction log. Corruption may occur |
| 129 | Reset to device, <device name>, was issued. |
| 1066 | Cluster disk resource Disk <x> : is corrupt. Running ChkDsk /F to repair problems. |
| 6008 | The previous system shutdown at <time> on <date> was unexpected. |
The errors are only related to SQL Server problems if the device or disk associated with the error is used to store SQL Server database or transaction log files.
The cause of these errors depends on the specific error but is usually related to a problem with a device driver, firmware, or hardware failure of a storage device.
The resolution of these errors depends on the specific error. Before you attempt to correct a SQL Server database inconsistency problem via restore or repair, you should carefully consider resolving the cause of any associated System Event Log error
You can visit the references for respective Event IDs from the list below to find more information about the event.
- Event ID 9
- 314093
(http://kbalertz.com/314093)
How to troubleshoot error messages about Event ID 9 and Event ID 11
- Event ID 11
- Details for Event ID 11
(http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=11&EvtSrc=disk&LCID=1033)
- Event ID 15
- Details for Event ID 15
(http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=15&EvtSrc=disk&LCID=1033)
- 154690Â
(http://kbalertz.com/154690)
How to troubleshoot event ID 9, event ID 11, and event ID 15 error messages
- 259237
(http://kbalertz.com/259237)
Troubleshooting event ID 9, 11, and 15 on Cluster Servers
- Event ID 50
- 816004 Â
(http://kbalertz.com/Feedback.aspx?kbNumber=http://kbalertz.com/816004/
)
Description of the Event ID 50 Error Message
- Details for Event ID 50
(http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=50&EvtSrc=ntfs&LCID=1033)
- Symantec's KB on this issue
(http://www.symantec.com/business/support/index?page=content&id=TECH21500)
- Event ID 51
- 244780
(http://kbalertz.com/244780)
Information about event ID 51
- Details for Event ID 51
(http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=51&EvtSrc=disk&LCID=1033)
- Event ID 55
- Details for Event ID 55
(http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=55&EvtSrc=ntfs&LCID=1033)
- 932578
(http://kbalertz.com/932578)
Event ID 55 may be logged in the System log when you create many files on an NTFS partition on a Windows Server 2003-based or Windows XP-based computer
- 885688
(http://kbalertz.com/885688)
Event ID 57, event ID 55, and event ID 50 may be logged when you use Windows Cluster on Windows Server 2003
(http://kbalertz.com/Feedback.aspx?kbNumber=932578)
- Event ID 57
- Details for Event ID 57
(http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=57&EvtSrc=ntfs&LCID=1033)
- Event ID 1066
- Event ID 1066 — Cluster Storage Functionality
(http://technet.microsoft.com/en-us/library/cc773419(WS.10).aspx)
- 317635
(http://kbalertz.com/317635)
ChkDsk Utility Runs on the Shared Cluster Hard Disk When You Bring a Physical Disk Resource Online
- 311081
(http://kbalertz.com/Feedback.aspx?kbNumber=311081)
Troubleshooting Multiple Cluster Symptoms on the Same SAN
- Event ID 6008
- Details for Event ID 6008
(http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.0&EvtID=6008&EvtSrc=User32&LCID=1033/)
- 196452
(http://kbalertz.com/196452)
Why Windows NT Reports 6005, 6006, 6008, and 6009 Event Log Entries
For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:
Collapse this tableExpand this table
Rule software
| Rule title
| Rule description
| Product versions against which the rule is evaluated |
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)
| This system experienced problems related to I/O requests.
This system experienced unexpected shutdowns
| The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect if any of the events listed in the Symptoms section are found in the Windows System Event Log. The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2. If you run the BPA tool and encounter an Error with the title of Engine - This system experienced problems related to I/O requests, then you have one of the EventID values as listed in the Symptoms section of this article in your Windows System Event Log. In all cases, the correct EventID is detected based on the message text or source (these EventID values can be used with other sources). BPA does not filter on any date/time so it will report the number of occurrences of these events in your current Event Log.Â
Another rule for SQL Server 2008 R2 BPA detects specifically EventID=6008 which is for unexpected system shutdowns. In some situations, an unexpected system shutdown can lead to consistency problems such as torn pages. This condition will be encountered if BPA detects an Error with the title of Engine - This system experienced unexpected shutdowns | SQL Server 2008
SQL Server 2008 R2
|
SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)
| This system experienced problems related to I/O requests.
This system experienced unexpected shutdowns
| The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect if any of the events listed in the Symptoms section are found in the Windows System Event Log.If you run the BPA tool and encounter an Error with the title of Engine - This system experienced problems related to I/O requests, then you have one of the EventID values as listed in the Symptoms section of this article in your Windows System Event Log. In all cases, the correct EventID is detected based on the message text or source (these EventID values can be used with other sources). BPA does not filter on any date/time so it will report the number of occurrences of these events in your current Event Log.Â
Another rule for SQL Server 2012 BPA detects specifically EventID=6008 which is for unexpected system shutdowns. In some situations, an unexpected system shutdown can lead to consistency problems such as torn pages. This condition will be encountered if BPA detects an Error with the title of Engine - This system experienced unexpected shutdowns | SQL Server 2012
|
APPLIES TO
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Workgroup Edition
- Microsoft SQL Server 2008 Developer
- Microsoft SQL Server 2008 Enterprise
- Microsoft SQL Server 2008 Express
- Microsoft SQL Server 2008 Express with Advanced Services
- Microsoft SQL Server 2008 R2 Datacenter
- Microsoft SQL Server 2008 R2 Developer
- Microsoft SQL Server 2008 R2 Enterprise
- Microsoft SQL Server 2008 R2 Express
- Microsoft SQL Server 2008 R2 Express with Advanced Services
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate