VMware Cloud Community
EasyIT
Contributor
Contributor

esxi 4.1 VM Tools crashing on SBS 2008

Hi All,

We recently upgraded drives on our server and as part of the process backed up all guests, added drives, reformated and installed esxi 4.1 (previous was 4.0) then put hosts back on to the new esxi 4.1 (via VMWare converter - from ShadowProtect images)

Since restoring our SBS 2008 has had problems - VM Tools keeps crashing and high CPU issues (anything we do on it seems to max the cpu).

Event log shows:

Application Error Event ID: 1000

Faulting application vmtoolsd.exe, version 8.3.2.1593, time stamp 0x4be64de9, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000374, fault offset 0x00000000000aef37, process id 0xb74, application start time 0x01cb33d309d26711.

System Log:

Event ID: 7031

The VMware Tools Service service terminated unexpectedly. It has done this 498 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.

We have tried uninstalling VM Tools and reinstalling but cannot get it stable.

Anyone have any ideas? Any help would be appreciated.

Cheers,

Jeremy

0 Kudos
4 Replies
DanInNH
Contributor
Contributor

I'm having the same problem with VMware Tools crashing after upgrading from ESXi 4.0 to 4.1. The VM is running Windows Server 2008 Standard running Exchange 2007. Like you I have uninstalled VMware Tools numerous times. The error I am getting is identical. Unlike EasyIT, I haven't noticed a problem with maxing out the the CPU.

The errors reported the event log are identical.

If anyone knows of a solution...

Thanks.

- Dan

0 Kudos
Bartman71
Enthusiast
Enthusiast

I am having the same issues with Windows XP SP3 VDIs running on ESX4.1 and ESXi4.1 - alle VM's which have have updated VMTools version 8 do have this issue. All VM's still running tools from latest 4.0 ESX edition are fine.

Marc

0 Kudos
zemitch
Enthusiast
Enthusiast

Having the same issue with Windows 2008 R2. Any fix available? Thanks.

0 Kudos
DanInNH
Contributor
Contributor

I was able to solve this with help from VMware support.  See http://communities.vmware.com/thread/283729?tstart=0.
0 Kudos