new1234.jpg

Archive

Posts Tagged ‘Error’

VMware: Error in the RPC receive loop: RpcIn: Unable to send.

November 20th, 2014 1 comment

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):

image

 

[ warning] [vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send.

 

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

 

This is correct:

image


Workaround

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

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , , , , ,

VMware: Error 2901. Could not connect to vCenter Single Sign On during install

August 26th, 2014 1 comment

Today I installed a new vCenter 5.5 server in a environment without a domain and DNS server. During the deployment of vCenter Single Sign On I received this error message:

Error 29101 Could not connect to vCenter Single Sign On. Make sure that the Lookup Service URL points correctly to the vCenter Single Sign On instance you installed. If vCenter Sign On is installed with an IP address, make sure the IP address is specified in the URL.

clip_image001

 

Solution:

image

Select: “Use FQDN instead of IP address to configure vCenter Single Sign-On”

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: View–Error 1920. Service VMware View Composer (svid) failed to start

January 9th, 2012 16 comments

Today I was installing VMware View in my homelab, after trying to install VMware View Composer 2.7 I received this error message:

Error 1920. Service VMware View Composer (svid) failed to start. Verify that you have sufficient privileges to start system services.

 

image

 

Solution:

After creating a new ODBC connection to my SQL server I still can’t finish the installation, the installation want to start service: VMware View Composer (svid).. after changing the logon service with the credentials I used for the ODBC I was able to start the service and finish the setup

image

 

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Non-VI workload detected on the datastore

February 11th, 2011 No comments

Today I saw some warnings on all of the datastores by a customer, here some warnings:

Non-VI workload detected on the datastore

 

image

An external I/O activity is detected on datastore “datastore”, this is an unsupported configuration. Consult the Resource Management Guide or follow the Ask VMware Link for more information

 

image

Summary

The purpose of this informational event is to alert the user of a potential misconfiguration or I/O performance issue caused by a non-ESX workload. It is triggered when Storage I/O Control (SIOC) detects that a workload that is not managed by SIOC is contributing to I/O congestion on a datastore that is managed by SIOC. (Congestion is defined as a datastore’s response time being above the SIOC threshold.) Specific situations that can trigger this event include:

  • The host is running in an unsupported configuration.
  • The storage array is performing a system operation such as replication or RAID reconstruction.
  • VMware Consolidated Backup or vStorage APIs for Data Protection are accessing a snapshot on the datastore for backup purposes.
  • The storage media (spindles, SSD) on which this datastore is located is shared with volumes used by non-vSphere workloads

SIOC continues to work during these situations. This event can be ignored in many cases and you can disable the associated alarm once you have verified that none of the potential misconfigurations or serious performance issues are present in your environment. As explained in detail below, SIOC ensures that the ESX workloads it manages are able to compete for I/O resources on equal footing with external workloads. This event notifies the user of what is happening, provides the user with the opportunity to better understand what is going on, and highlights a potential opportunity to correct or optimize the infrastructure configuration.

This KB article will help you understand what is causing the event, and what, if any, action is required to address the cause.

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn