Search the VMware Knowledge Base (KB)
View by Article ID

Upgrading to VMware Tools 5.1 reports the message: Error in the RPC receive loop: RpcIn: Unable to send (2036350)

  • 427 Ratings


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.


    [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.


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.


This issue is resolved in VMware ESXi 5.1 Patch 3, available at VMware Downloads. For more information, see VMware ESXi 5.1, Patch Release ESXi510-201310001 (2053402)

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\

    • Windows Vista, Windows 7, and Windows Server 2008:

      C:\ProgramData\VMware\VMware Tools\

    • Linux:


    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:

    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. In 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 then power it on.
  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.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Update History

09/28/2012 - Added that this can also be seen on non Terminal Servers 01/29/2013 - Added additional error to Symptoms 01/29/2013 - Added note to regarding killing the vmtoolsd.exe process.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 427 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 427 Ratings