Search the VMware Knowledge Base (KB)
View by Article ID

Creating a quiesced snapshot of a Windows virtual machine generates Event IDs 50, 57, 137, 140, 157, or 12289 (2006849)

  • 430 Ratings

Symptoms

When using the new version of VMware Tools in ESXi/ESX 4.1 Update 1 or newer, you experience these symptoms:
  • When a quiesced snapshot is created on a Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or a Windows Server 2012 R2 virtual machine, duplicate disks are created in the virtual machine.
  • The Event Viewer in the virtual machine displays one or more of these events:

    • Event ID: 50 NTFS Warning
      {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

    • Event ID: 57 NTFS Warning
      The system failed to flush data to the transaction log. Corruption may occur.

    • Event ID: 137 NTFS Error
      The default transaction resource manager on volume \\?\Volume{806289e8-6088-11e0-a168-005056ae003d} encountered a non-retryable error and could not start. The data contains the error code.

    • Event ID: 140 NTFS Warning
      The system failed to flush data to the transaction log. Corruption may occur in VolumeId:<> DeviceName: \Device\HarddiskVolume<>.(A device which does not exist was specified.).

    • Event ID: 157 Disk Warning
      Disk x has been surprise removed.

Resolution

This is a known issue affecting VMware ESXi 4.x, 5.x, and 6.0.
 
Currently, there is no resolution.

To work around this issue, see the Microsoft Knowledge Base article 2853247 and 885688.

Note: The preceding links were correct as of November 25, 2015. If you find a link is broken, provide feedback and a VMware employee will update the link.

Additional Information

This table provides more information about the events:

Event Description
Event ID 50 NTFS Warning The NTFS filesystem sees the volume as read-write. The volume is actually read-only so these operations fail to start and no modifications are made to the volume.
Event ID 57 NTFS Warning This is misleading as no actual corruption occurs. The volume is actually read-only, so these operations fail and no modifications are made to the volume.
Event ID 137 NTFS Warning The NTFS filesystem sees the volume as read-write. The volume is actually read-only so these operations fail and no modifications are made to the volume.
Event ID 140 NTFS Warning This is misleading as no actual corruption occurs. The volume is actually read-only, so these operations fail and no modifications are made to the volume.
Event ID: 12289 VSS Error This message is benign. This occurs when the virtual machine drives are queried to determine which are eligible for snapshots, and the floppy drive is not eligible.
Event ID: 157 Disk Warning This message is benign.  The volume is actually read-only, so these operations fail and no modifications are made to the volume.

Note: To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Update History

07/16/2012 - Added ESX/ESXi 4.1 Update 2 and ESXi 5.0 in Symptoms and Products sections 08/20/2012 - Added information about Event IDs 02/06/2013 - Added ESXi 5.1 to Product Versions. 01/15/2014 - Added ESXi 5.5 to Product Versions. 11/18/2015 - Added VMware ESXi 6.0.x Product Version.

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

  • 430 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)




Please enter the Captcha code before clicking Submit.
  • 430 Ratings
Actions
KB: