VMTools Warning-EVENT ID 1000: [warning][vmuser:vmuser] SOCKET failed to create socketm error 10106

I have seen this issue many times in windows server 2003 R2. specially, when i upgrade my environment into latest build.After that VMTools warning message arrived. it will generate tons of event log s.Why this problem arrived is due to various reasons. you can find more about at following VMWare KB 2036350


When VM Tools warning message starts. you will see the windows event log is full of VMTools warning message as shown below.

Vmtools error in w2k3-01

To work around this issue, disable VMware Tools logging to the Event Log and general virtual machine logging to the vmware.log file for the virtual machine.

Note:  If you encounter issues with VMware Tools, the logging will need to be enabled again for troubleshooting.

To disable VMware Tools application event logging:

  1. Open the tools.conf file using a text editor. The tools.conf file is located at:
    • Windows XP and Windows Server 2000/2003:C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\ (in my case)
    • Windows Vista, Windows 7, and Windows Server 2008:C:\ProgramData\VMware\VMware Tools\
    • Linux:/etc/vmware-tools/tools.conf

when i go to above mentioned path. i saw there is no file with name tools.conf exists. if this is same with you. then create a file by yourself.

Vmtools error in w2k3-02

Create a file with name tools.conf and edit it with notepad or any other editor as shown below.

Add this section to the tools.conf file:

vmusr.level = error
vmsvc.level = error

Vmtools error in w2k3-03

Save and close the file.

Restart the VMTools service (Administrative Tools > Services).

Vmtools error in w2k3-04

Note: If there are users logged in to more than one session, restarting the VMTools service may not be sufficient. You may have to kill the vmtoolsd.exe process for all instances.


Now if you go to Event Logs of your VM. you will see there is no more warning events for VM Tools.

Vmtools error in w2k3-05


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s