(vCenter service was down)
* If your vCenter is a Windows installed, the first thing to check are the windows event logs. There will likely be entries in the event logs relating to the vCenter service issue, such as
Could not start the VMware VirtualCenter Server service on Local Computer. Error 1067: The process terminated unexpectedly.
* The next thing to check is the vCenter server log file (vpxd.log) you may see an error similar to
[2017-03-30 14:41:37.687 02128 error 'App'] [VpxdReverseProxy] Failed to create http proxy: An attempt was made to access a socket in a way forbidden by its access permissions.
[2017-03-30 14:41:37.687 02128 error 'App'] [Vpxd::ServerApp::Init] Init failed: VpxdMoReverseProxy::Init()
[2017-03-30 14:41:37.687 02128 warning 'VpxProfiler'] ServerApp::Init took 29328 ms
[2017-03-30 14:41:37.687 02128 error 'App'] Failed to intialize VMware VirtualCenter. Shutting down...
[2017-03-30 14:42:14.359 02128 info 'App'] Forcing shutdown of VMware VirtualCenter now
The first thing to do is confirm that vCenter cannot be started by attempting a manual restart of the vCenter service.
A common issue when the service won’t start is that there is a problem with the vCenter server database. This can be checked by testing the ODBC link to determine whether you can connect to the database server. Also, Check the vCenter service is running with the correct credentials.
(host disconnects from vCenter Server) From VMware KB
* This issue occurs when heartbeat packets are dropped, blocked, or lost between the vCenter Server and the ESXi/ESX host.
* If there is an incorrect configuration of the vCenter Server managed IP address, the host receives the heartbeat from vCenter Server, but cannot return it.
* It is important to remember that the default heartbeat port is UDP 902, and these packets must be sent between vCenter Server and the ESXi/ESX host for the host to stay connected and remain in the vCenter Server inventory.
* If the host is not connecting to vCenter Server at all, the cause may be another network issue."
VMware VDI Administrator.
Stay Connected Don't forget to:
Like > Share > Comment > Reply > Helpful > Answered