"com.vmware.vim.binding.eam.fault.NoConnectionToVCenter" error

Products

• VMware vCenter Server

Issue/Introduction

Upgrading to vCenter Server 6.0.0a resolves the issue.

Symptoms:

• Querying an NSX prepared cluster for deployment status fails
• Installation status at the NSX Manager User Interface (UI) and the API output shows incorrect values.
• In the /home/secureall/secureall/logs/vsm.log file, you see the error:
  
  WARN EamConnectionKeepaliveThread VcEamConnection:170 - EamConnection not connected com.vmware.vim.binding.eam.fault.NoConnectionToVCenter:
  

Cause

This issue occurs when the vCenter Server daemon (vpxd) goes down immediately after it comes up on a host due to a rare timing issue. The vCenter Server loses its connection to ESX Agent Manager (EAM) and NSX is unable to query the deployment status of its components on clusters from ESX Agent Manager.

Rebooting NSX Manager or un-registering and re-registering it with vCenter Server does not resolve this issue as the root cause is a connection failure between vCenter Server and EAM.

Resolution

This issue is resolved in VMware vCenter Server 6.0.0a, available at VMware Downloads.

To work around this issue if you do not want to upgrade, restart the EAM services.

To restart the EAM Service:

1. Log in with proper credentials using the vSphere Web Client.
2. Navigate to Home > Administration.
   
3. Click System Configuration.
4. Click Services.
5. Right-click VMware ESX Agent Manager.
6. Click restart.