Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Windows 2008 R2 virtual machine using a paravirtual SCSI adapter reports the error: Operating system error 1117 encountered (2004578)

Symptoms

  • On an ESX/ESXi 4.0 U1, ESX/ESXi 4.1, or ESXi 5.0 host, in a Windows 2008 or Windows 2008 R2 virtual machine using a paravirtual SCSI adapter, Microsoft Exchange Server 2007 or  Microsoft Exchange Server 2010 or SQL Server 2008 or SQL Server 2008 R2 reports an error.
  • In the Event Viewer, you see one or more of these errors:

    • Error: 17053, Severity: 16, State: 1.
      LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered

    • SQL Error: 823, Severity: 4, State: 3
      The operating system returned error 1117(The request could not be performed because of an I/O device error.) to SQL Server during a write at offset <offset> in file <dbfile.mdf>.


    • Error: 17053, Severity: 16, State: 1.
      ReadFileHdr: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.

    • Microsoft.Exchange.Cluster.ReplayService (2552) Recovery E02 WKSEPMBX02\Storage Group 3: An attempt to write to the file "P:\SG3-DB\WKSEPMBX02-SG3-MDB1.edb" at offset 2007040 (0x00000000001ea000) for 8192 (0x00002000) bytes failed after 0 seconds with system error 1117 (0x0000045d): "The request could not be performed because of an I/O device error. ". The write operation will fail with error -1022 (0xfffffc02). If this error persists then the file may be damaged and may need to be restored from a previous backup.

Purpose

This article describes a specific issue. If you are experience some, but not all, of these symptoms, your issue is not related to this article. If you are experiencing an issue with your host or guest, search for your symptoms in the Knowledge Base or Open a Support Request.

Resolution

This is a known issue affecting VMware ESX/ESXi 4.0 U1, ESX/ESXi 4.1, and ESXi 5.0.
 
This issue is resolved in vSphere 5.0 Update 1 and vSphere 5.1. For more information, see the VMware ESXi 5.0 Update 1 Release Notes.
 
To resolve this issue in ESXi 4.1 and earlier versions, apply the patch VMware ESXi 4.1 Patch ESXi410-201201402-BG. For more information, see VMware ESXi 4.1 Patch ESXi410-201201402-BG: Updates VMware Tools (2009144).

Workaround

To work around this issue, change the SCSI Controller type from VMware Paravirtual to LSI Logic SAS.

Note: Microsoft Knowledge Base article 2519834 appears to recommend using an LSI Logic Parallel controller. VMware recommends using the LSI Logic SAS virtual SCSI controller for Windows 2008 guests.

Note: The preceding link was correct as of November 7, 2011. If you find the link is broken, provide feedback and a VMware employee will update the link.

To change the SCSI Controller type:

  1. Power off the virtual machine.
  2. Right-click the virtual machine.
  3. Click Edit Settings.
  4. Select SCSI Controller.
  5. Click Change type.
  6. Change VMware Paravirtual to LSI Logic SAS.

See Also

Update History

02/29/2012 - Added information on patch for ESXi 4.1 and earlier releases. 03/22/2012 - Added information that the issue is resolved in vSphere 5.0 Update 1 and added a link to the Release Notes

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 14 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 14 Ratings
Actions
KB: