An error occurred while communicating with the remote host

[Poestges]

Hi community,

I have a problem with my VC2.5 and ESX3.5.

50% of all actions results in "An error occurred while communicating with the remote host". The 2nd try mostly works, sometimes i have to do another try.

I start an action, the host disconnects and a few seconds later the host is back and i can give it another try. The error occures on every host i have.

Can anyone help me, please?

TIA,

Sascha

[RegNullify]

Greetings,

Yes, I did remove "Converter" through add/remove programs. I removed both the "Converter" and the "Converter Agent". I don't recall if I rebooted the machine or not. I don't think you need to. Anyway I hope this helps resolves your issue. Please let us know your results. Thanks for your support.

-Reg

[Ph_Seifert]

Hi @all,

thanks for the information in this thread. I wrote to the vmware support but without solving this problem. I hope to fix the problem with the uninstallation of Converter and Update Manager. At the moment everything works fine. I'll report too.

kind regards

Philipp

[Ph_Seifert]

I have bad news. The Problem isn't fixed. When I want to migrate on VM to another host the action stopped with teh An error occurred ... message. When I then restart the Virtual Center Service on the VC host everything works fine. How long it will work? Its sporadically.

[Travis_Wood]

This has been fixed in the VC Update 5

http://www.vmware.com/support/vi3/doc/vi3_vc25u5_rel_notes.html#resolvedissues

[GPavan]

Hi All,

I've received same error "An error occurred while communicating with the remote host". Here What i want to know is does it records any event errors on VC center concole? Please advice. Thanks in advance.

[Evilnerd]

I was having this issue as well and here is ths steps I had to do to get it working.

1.logged into Vcenter and disconnected each of my cluster nodes

2. Removed each node after the disconnect completed

3. Logged into each cluster node seperately and ran to validate the vcenter agent was running service vmware-vpxa status

4. Stop the vcenter agent service vmware-vpxa stop

5. locate the vcenter agetn version and package to remove rpm -qa | grep -i vpxa

6. Remove teh vcenter agent rpm -e VMware-vpxa-4.0.0-208111

7. Restart the vmware management service service mgmt-vmware restart

8. Log into each ESX host by IP just to validate the management service came up and your able to view your VMs

9. Log into the Vcenter server and restart the VMware VirtualCenter Server windows service

10. Log into Vcenter from the Vsphere client and readd your nodes to the cluster

11. I had to renable HA on each node in order to clear all alarms after they were initially added

These steps fixed the issue for me

[the_norris]

hi Evilnerd.

We are having the same issue here - vsphere 4.1 esxi hosts and vc4. All patches as of last week applied. System was upgraded from 3.x.

Problem include: connect host in to VC, power operations on VMs, and VM migrations.

Now not sure what triggered the issues - but two things happen 1) New version of Trend AV client installed onto the VC, and the SQL server hosting the VCDB when down (not clean shutdown).

I thought the problems was only limited to 4 hosts that were powered down for datacenter power work been done. All 4 hosts and hosts VMs powered down cleanly.

Then I found this is is effecting all hosts connected to the VC.

I can connect the VI client to the 4 hosts that was downed directly to start the critical VMs needed for Monday start of business.

I've opened a SR with VMWare yesterday - but need to wait until Monday as only have Basic support.

Phil

[stripe]

This happened me on Dell servers with Broadcom onboard NICs, where if there was an signle VLAN adapter without trunk made ping responses to vmkernel within data transfer in hundreds of ms, in some whiles complete packet loss. So vcenter killed the session and the host reconnocted successfully after cleanup of the network.

Resolution was to do some activity in console, use a wider connection to switch or use of another NIC brand like Intel.

[harishraman01]

It is DNS Issue , verify the DNS entry to resolve the host on network is right !

in my case the host had wrong DNS entry , thereby the hostname was not getting resolved and had this error, after keying in the correct DNS ip , it worked ..