«

»

Jun 23 2015

Can’t connect to vCenter Server – connection timeout

“VMTurbo"

So i few days back i ran into a problem while connecting to vCenter Server version 5.5 U2d i have never seen before.
Neither the vSphere Web Client or the vSphere Client managed to connect to the vCenter Server. I just received connection timeout messages. I did actually try to login, using the vSphere Client, from the Windows Server 2012 R2 based virtual machine (VM) running the vCenter Server application. That also failed.
The following steps were taken during my investigation:
  • Verified all vCenter Server related services were up and running
  • Verified that the anti-virus installed in the VM was not blocking connections.
  • Verified that the local firewall did not block our connections.
  • Investigated the vCenter Server log files:
    • The only thing i could find was the following in the Inventory Service log file:
      • ProviderManagerServiceImpl Error fetching resources: com.vmware.vim.query.server.store.exception.ResourceRetrievalException: org.apache.http.conn.HttpHostConnectException: Connection to 443 refused
  • Verified the Windows Server Event logs and found the following in the System event log:
    • Event: 4227 Tciip with level warning:
      • TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.
    • Event: 23 Eventlog with level Error
      • The event logging service encountered an error (res=1500) while initializing logging resources for channel Microsoft-Windows-PushNotification-Platform/Admin
    • Event 25 Eventlog with level Info
      • The event logging service encountered a corrupt log file for channel Microsoft-Windows-FileServices-ServerManager-EventProvider/Operational. The log was renamed with a .corrupt extension.

Based on my findings i decided to restart all the vCenter Server related services but that didn’t help.

I then decided to reboot the VM and that actually made all the event log entries, the vCenter Server Inventory Services error disappear and i could connect to the vCenter Server.

I have asked the customer to create SRs to both Microsoft and VMware so we can get an understanding of why this happened. Will update the post with additional information when i get som feedback.

2 comments

  1. Dhaval

    Have you got any information onit from VMWare support! !?

  2. magander3

    Hi,
    no nothing yet

    //Magnus

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">