I am seeing a strange occurrence with regard to vmware tools and MS Windows Updates.
For one VM, I have been running NAKIVO backup software without any issues. NAKIVO used VMware snapshots as the mechanism to backup up the VM by using QUIESCING. After an MS Update occurred on April 13, the backup process began failing with an error - An error occurred while taking a snapshot: msg.snapshot.error-QUIESCINGERROR. I confirmed this by trying to take a snapshot and selecting the Quiesce option.
Has anyone seen or heard of MS Updates affecting snapshots?
On the other VM, after a the same MS update occurred, I am seeing a message in vcenter events.,, cannot quiesce this virtual machine because VMware Tools is not currently available.
Has anyone seen or heard of MS Updates affecting VMware Tools ?
It sounds like the VMware Tools Service may not be running in the appropriate VM. Check your services to ensure VMware Tools is running and started to run automatically. Also, you may wish to upgrade/repair VMware Tools on the VM.
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009-2016
Author of the books 'VMWare ESX and ESXi in the Enterprise: Planning Deployment Virtualization Servers', Copyright 2011 Pearson Education. 'VMware vSphere and Virtual Infrastructure Security: Securing the Virtual Environment', Copyright 2009 Pearson Education.
We are seeing the exact same thing.
To temporarily solve it, you need to login into the server and restart the "VMware Tools" and "VMware Snapshot Provider" services. You will get an error when trying to restart the "VMware Tools" service. After the error you can just start the service again and everything will work fine until the next time the server reboots.
The problem seems to be the "VMware tools" service which stops responding when asked to quiesce the file system.
This happens on both Windows Server 2008 R2 and Windows Server 2012 R2 with the newest VMware Tools available
sounds like the same problem which we have (see: Sometimes VMware tool service is not running on Windows 2012 R2 guest VM on ESXi6.0), somebody knows which update is the cause of this mess?
I've been experiencing the same thing for a couple of months now in 5.5. I originally thought upgrading from tools 10240 to 10246 had resolved it, but I discovered after Windows OS patching that the issue returned. I certainly hope they have this resolved well before the end of the year. That's way too long to let a problem like this stick around. I am experiencing this on pretty barebones Windows VMs, so I imagine many customers are being negatively impacted by this. Backup software relies on this functionality working correctly.
It seems the KB article is now available for this problem:
It says ESXi 6.0 Patch 02 (ESXi600-201505001) but we have the same problem in 5.5 Update 2B.
Hopefully this will be fixed soon!
Thanks for linking to that KB. So it appears VMware has acknowledged the issue for 6.0 at least. We're on 5.5 Update 3b and experiencing this issue, so you're correct, 5.5 needs a fix too!
CAN SOMEONE PLEASE LOOK AT MY POST INCLUDING SCREENSHOTS AND TELL ME IF I HAVE THE SAME ISSUE?
Also, I am using ESXi 6.0U2 Custom HP image to pull VMware Tools on Win12R2.
Will I be affected if I use new non-custom VMware Tools. Will it overwrite drivers?
The latest VMware tools are 10.1.5 2017-02-23 will they resolve this issue?
I think you are barking up the wrong tree. VMware Tools uses VSS to quiesce the virtual machine before taking the snapshot. Run "VSSADMIN LIST WRITERS" from the Windows CLI (DOS window) As Administrator. If any of the VSS Writers are not in State 1 (Stable) then VSS will not be able to quiesce the VM and the backup will fail with that error.