VMTOOLS WARNING-EVENT ID 1000: [WARNING][VMUSER:VMUSER] SOCKET FAILED TO CREATE SOCKETM ERROR 10106
轉載至
https://vmexpo.wordpress.com/2015/10/24/vmtool-warning-event-id-1000-warningvmuservmuser-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
Solution:
When VM Tools warning message starts. you will see the windows event log is full of VMTools warning message as shown below.
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:
- 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.
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:
[logging]
vmusr.level = error
vmsvc.level = error
Save and close the file.
Restart the VMTools service (Administrative Tools > Services).
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.
Verify:
Now if you go to Event Logs of your VM. you will see there is no more warning events for VM Tools.
=======================================================================
Symptoms
After upgrading a Terminal Server or Terminal Server-based Citrix XenApp virtual machine to VMware Tools 5.1, you experience these symptoms:
- In the Windows Application Event log, you see this error reported multiple times in quick succession (log spew):
Error in the RPC receive loop: RpcIn: Unable to send.
- On a Linux guest operating system, you see log spews similar to:
vmusr[2116]: [warning] [vmusr] Error in the RPC receive loop: RpcIn: Unable to send.
or
[warning] [vmsvc:guestinfo] Conversion to UTF-8 failed
[warning] [vmsvc:guestinfo] Failed to get vmstats
- User instances of
vmtoolsd fails with this error:
Access violation (0xC0000005)
- You cannot map network drives.
- You experience disconnected terminal sessions.
Note: This issue may also occur on non-Terminal Servers, such as Windows 2008, Windows 2003, and Linux distributions.
Cause
This issue occurs when the VMware Tools daemon (vmtoolsd) handles more than two Terminal Sessions. When a user connects to a Windows virtual machine, each terminal session should have one vmtoolsd running. However, vmtoolsd is limited to only two sessions running simultaneously.
Thus, the Windows Application Event log fills up with warning messages similar to this until the total connection count is > 2 per session:[vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send.
Resolution
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:
- 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\
- Windows Vista, Windows 7, and Windows Server 2008:
C:\ProgramData\VMware\VMware Tools\
- Linux:
/etc/vmware-tools/tools.conf
For more information, see the Configuration File Location section in Enabling debug logging for VMware Tools within a guest operating system (1007873).
Note: If the tools.conf file is not present, create the file manually using a plain text editor.
- Add this section to the tools.conf file:
[logging]
vmusr.level = errorvmsvc.level = error
- Save and close the file.
- Restart the VMTools service (Administrative Tools > Services).
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.
To disable general virtual machine logging:
- Click the virtual machine in the Inventory.
- In the Summary tab for that virtual machine, click Edit Settings.
- In the virtual machine Properties dialog box, click the Options tab.
- Under Advanced, click General and deselect Enable logging.
- Click OK to save the change.
- To make the change take effect, power off the virtual machine and then power it on.
- If the issue continues, try uninstalling and reinstalling VMware Tools.
Note: If you do not want to power off your virtual machine to disable logging, you can also use vMotion to migrate the virtual machine after changing this setting.
See Also
沒有留言:
張貼留言