Upgrading to VMware Tools 5.x causes log spew with the message: Error in the RPC receive loop: RpcIn

        在使用vmtool时，系统的日志当中没隔一秒机会出现[ warning] [vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send.的错误。这个问题发生在VMware工具守护进程(vmtoolsd)处理两个多终端会话。当用户连接到Windows虚拟机,每个终端会话应该有一个vmtoolsd运行;然而,vmtoolsd仅限于只有两个会话同时运行。

vmware官网给出的详细解释及解决办法：

Symptoms

After upgrading a Terminal Server or Terminal Server-based Citrix XenApp virtual machine to VMware Tools 5.x, 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 OS, you see log spew of:
  
  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
  
  
• In the vmware.log file located at, /vmfs/volumes/virutal_machine_datastore/virtual_machine_folder/, for the virtual machine. You see this log spew:
  
  GuestRpc: Channel X, conflict: guest application toolbox-dnd tried to register, but it is still registered on channel Y
GuestRpc: Channel X reinitialized.
  
  
• User instances of vmtoolsd crash with this error:
  
  Access violation (0xC0000005)


• You cannot map network drives. 
  
• You are experiencing disconnected terminal sessions.
  

Note: This issue may also occur on non-Terminal Servers, such as Windows 2008 and 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.

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\
     
     
   • 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.
   
   
2. Add this section to the tools.conf file:
   
   [logging]
   vmusr.level = error
   vmsvc.level = error
   
   
3. Save and close the file.
4. 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:

1. Click the virtual machine in the Inventory.
2. On the Summary tab for that virtual machine, click Edit Settings.
3. In the virtual machine Properties dialog box, click the Options tab.
4. Under Advanced, click General and deselect Enable logging.
5. Click OK to save the change.
6. To make the change take effect, power off the virtual machine and power it back on again.
7. 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.