1 2 Previous Next 22 Replies Latest reply on Oct 5, 2017 7:16 AM by dirch201110141

    a connection error occurred. verify that your computer can connect to vcenter server

    Dreher Enthusiast

      friends

      I can not deploy an OVF, the following message appears: "a connection error occurred. verify that your computer can connect to vcenter server"

        • 1. Re: a connection error occurred. verify that your computer can connect to vcenter server
          Richardson Porto Champion
          Community WarriorsUser Moderators
          ---

          Richardson Porto
          Senior Infrastructure Specialist
          LinkedIn: http://linkedin.com/in/richardsonporto
          • 2. Re: a connection error occurred. verify that your computer can connect to vcenter server
            Dreher Enthusiast

            I'm using vCenter and ESXi 5.5 update 2, I'm not using the 5.1 ...

            • 3. Re: a connection error occurred. verify that your computer can connect to vcenter server
              jbaustert Novice

              Same problem here with latest vCenter 5.5 update 2.  Looks like they may have fixed it for vCenter 5.1 but didn't manage to bring the fix forward.

               

               

              JB

              • 4. Re: a connection error occurred. verify that your computer can connect to vcenter server
                mbowers6288 Lurker

                I have the same issue and I am using ESXi\ vCenter 6.0.0B

                • 5. Re: a connection error occurred. verify that your computer can connect to vcenter server
                  Andre39 Novice

                  Same problem vCenter 6.0b and only one vNIC and only one DNS entry for the FQDN and the IP address.

                  • 6. Re: a connection error occurred. verify that your computer can connect to vcenter server
                    FabienViapass Lurker

                    Same problem with vCenter 5.5 U2, someone has found a solution ?

                    • 7. Re: a connection error occurred. verify that your computer can connect to vcenter server
                      miloszmodrzewski Lurker

                      I'm using vCenter appliance 6.0 and try to install vCenter replication appliance 6.0 from ovf template. I have two sites with the same configuration (only hardware is different). On both sites I have the same problem as the author of this post. I have also one vnic connected to vCenter appliance, SSO implemented and DNS names resolved correctly.

                      • 8. Re: a connection error occurred. verify that your computer can connect to vcenter server
                        npadmani Master
                        VMware EmployeesvExpert

                        Did you try vSphere Client to do the same activity?

                        • 9. Re: a connection error occurred. verify that your computer can connect to vcenter server
                          miloszmodrzewski Lurker

                          I'm not sure if installing ova template from old application based client is even supported. I'll try it and let you know.

                          • 10. Re: a connection error occurred. verify that your computer can connect to vcenter server
                            miloszmodrzewski Lurker

                            When loading template trough vSphere Client 5.5.0 i get error msg:

                             

                            Line 342: Unsupported section 'vServiceDependencySection' (vCenter Extension vService Dependency).

                            • 11. Re: a connection error occurred. verify that your computer can connect to vcenter server
                              ChrisKuhns Enthusiast

                              Same problem here. First, I can't even load up the OVF from the Chrome or IE browsers. Now, the Opera browser I installed to work with the Client Integration Plug-in is giving me this error.

                              • 12. Re: a connection error occurred. verify that your computer can connect to vcenter server
                                bansne Enthusiast

                                It could be a DNS issue. Try forward and reverse DNS lookup on the DNS name of your vCenter server and that your vCenter server is using that DNS server as well.

                                • 13. Re: a connection error occurred. verify that your computer can connect to vcenter server
                                  miloszmodrzewski Lurker

                                  I'm using the same DNS server for VCSA and computer that I'm connecting to the VCSA trough web interface.. The DNS/reverse lookups are working correctly from the host for the VCSA host name and FQDN (this is a domain environment). Also in VCSA the hostanme/DNS is set correctly (vSphere 6.0 Documentation Center).

                                  • 14. Re: a connection error occurred. verify that your computer can connect to vcenter server
                                    brianhlarose Lurker
                                    VMware Employees

                                    Thanks for all the suggestions. I have some GOOD information now to help us.

                                     

                                     

                                    I have tried uploading an OVA file from the vsphere client, rather than the webclient and it works well.  I was able to upload the 1st VM from the webclient and then after that, it kept giving me this same error message

                                    a connection error occurred. verify that your computer can connect to vcenter server'.

                                    I am checking the DNS setting for FQDN name and everything appears to be ok there.  I am going to go back thru the settings and set EVERYTHING correctly again.. (heck, I might re-install ESX just to make sure).

                                     

                                    MORE DATA:

                                    1)  I can power OFF, or POWER ON machines from the Virtual Center Web Client, so we are communicating OK for those operations.

                                    2)  Deploy still fails.

                                     

                                    looking into the log files on the ESX host I see:

                                     

                                    => vmkernel.log <==

                                    2015-10-16T13:13:20.004Z cpu2:48709)World: 14299: VC opID HB-host-403@353-7ce7f297-f2 maps to vmkernel opID 28c702d8

                                     

                                    ==> hostd.log <==

                                    2015-10-16T13:13:27.572Z [FF99EB70 verbose 'SoapAdapter'] Responded to service state request

                                     

                                    ==> vmkernel.log <==

                                    2015-10-16T13:13:40.005Z cpu3:34052)World: 14299: VC opID hostd-44aa maps to vmkernel opID 404774ef



                                     

                                    ==> hostd.log <==

                                    2015-10-16T13:14:46.598Z [5D881B70 verbose 'Hostsvc.ResourcePool ha-root-pool'] Root pool capacity changed from 3691MHz/4959MB to 3691MHz/4958MB

                                    2015-10-16T13:14:46.601Z [5D840B70 verbose 'Default' opID=SWI-7708eafa user=vpxuser] AdapterServer: target='vim.ResourcePool:ha-root-pool', method='GetConfig'

                                    2015-10-16T13:14:46.602Z [FF99EB70 verbose 'Default' opID=SWI-7708eafa user=vpxuser] AdapterServer: target='vim.ResourcePool:ha-root-pool', method='GetName'

                                     

                                    ==> vpxa.log <==

                                    2015-10-16T13:14:46.600Z [5AFBBB70 verbose 'VpxaHalCnxHostagent' opID=WFU-1733fc25] [WaitForUpdatesDone] Received callback

                                    2015-10-16T13:14:46.600Z [5AFBBB70 verbose 'VpxaHalCnxHostagent' opID=WFU-1733fc25] [VpxaHalCnxHostagent::ProcessUpdate] Applying updates from 464 to 465 (at 464)

                                    2015-10-16T13:14:46.600Z [5AFBBB70 verbose 'VpxaHalResourcePool' opID=WFU-1733fc25] [VpxaHostdSpecSync] Received change notification from hostd ...

                                    2015-10-16T13:14:46.600Z [5AFBBB70 verbose 'VpxaHalResourcePool' opID=WFU-1733fc25] [VpxaHostdSpecSync] [IsVmListChangeUpdate] returning false

                                    2015-10-16T13:14:46.600Z [5AFBBB70 verbose 'VpxaHalResourcePool' opID=WFU-1733fc25] [VpxaHostdSpecSync] Setting _syncPending = true ...

                                    2015-10-16T13:14:46.600Z [5AFBBB70 verbose 'VpxaHalResourcePool' opID=WFU-1733fc25] [VpxaHostdSpecSync] Launching ProcessResourceNotification in new thread...

                                    2015-10-16T13:14:46.600Z [5AFBBB70 verbose 'VpxaHalCnxHostagent' opID=WFU-1733fc25] [WaitForUpdatesDone] Starting next WaitForUpdates() call to hostd

                                    2015-10-16T13:14:46.600Z [5AF79B70 info 'VpxaHalResourcePool' opID=SWI-7708eafa] GetOverrideFailureCount() = 0MAX_CONSECUTIVE_OVERRIDE_FAILURES = 3

                                    2015-10-16T13:14:46.600Z [5AFBBB70 verbose 'VpxaHalCnxHostagent' opID=WFU-1733fc25] [WaitForUpdatesDone] Completed callback

                                    2015-10-16T13:14:46.602Z [5AF79B70 verbose 'VpxaHalResourcePool' opID=SWI-7708eafa] [VpxaHalResourcePoolCurrentImpl::SetCachedRootResources] done

                                    2015-10-16T13:14:46.602Z [5AF79B70 verbose 'VpxaHalResourcePool' opID=SWI-7708eafa] [VpxaHostdSpecSync] Copied root values ...

                                    2015-10-16T13:14:46.602Z [5AF79B70 verbose 'VpxaHalResourcePool' opID=SWI-7708eafa] [ProcessResourceNotification] No syncs pending, exiting loop...

                                     

                                    ==> vmkernel.log <==

                                    2015-10-16T13:14:54.278Z cpu2:34045)World: 14299: VC opID hostd-0e20 maps to vmkernel opID d000f8aa

                                     

                                    ==> hostd.log <==

                                    2015-10-16T13:14:57.583Z [FFC40B70 verbose 'SoapAdapter'] Responded to service state request


                                    AND

                                    ==> vmkernel.log <==


                                     

                                    2015-10-16T13:15:00.005Z cpu0:48709)World: 14299: VC opID hostd-e64d maps to vmkernel opID 3c57020f

                                     

                                    ==> syslog.log <==

                                    2015-10-16T13:15:01Z crond[33577]: crond: USER root pid 49228 cmd /sbin/hostd-probe ++group=host/vim/vmvisor/hostd-probe

                                     

                                    ==> vpxa.log <==

                                    2015-10-16T13:15:01.138Z [FFBC0B70 info 'commonvpxLro' opID=SWI-13ad18a1-3f] [VpxLRO] -- BEGIN task-internal-272 --  -- vpxapi.VpxaService.fetchQuickStats -- 02b8b8de-6da3-6a12-d7f9-e5e0d5ec6fde

                                    2015-10-16T13:15:01.139Z [FFBC0B70 verbose 'vpxavpxaVmomi' opID=SWI-13ad18a1-3f] [VpxaVmomi] SetStatusDone was called with syncGenNo (353)

                                    2015-10-16T13:15:01.139Z [FFBC0B70 info 'commonvpxLro' opID=SWI-13ad18a1-3f] [VpxLRO] -- FINISH task-internal-272 --  -- vpxapi.VpxaService.fetchQuickStats --

                                     

                                    ==> hostd-probe.log <==

                                    Section for VMware ESX, pid=49229, version=5.5.0, build=2068190, option=Release

                                    2015-10-16T13:15:01.336Z [FF8CD7E0 info 'Default'] Logging uses fast path: true

                                    2015-10-16T13:15:01.336Z [FF8CD7E0 info 'Default'] Handling bora/lib logs with VmaCore facilities

                                    2015-10-16T13:15:01.336Z [FF8CD7E0 info 'Default'] Initialized channel manager

                                    2015-10-16T13:15:01.336Z [FF8CD7E0 info 'Default'] Current working directory: /var/log/vmware

                                    2015-10-16T13:15:01.337Z [FF930B70 info 'ThreadPool'] Thread enlisted

                                    2015-10-16T13:15:01.337Z [FF971B70 info 'ThreadPool'] Thread enlisted

                                    2015-10-16T13:15:01.338Z [FF9B2B70 info 'ThreadPool'] Thread enlisted

                                    2015-10-16T13:15:01.338Z [FF9F3B70 info 'ThreadPool'] Thread enlisted

                                    2015-10-16T13:15:01.338Z [FF8CD7E0 info 'ThreadPool'] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 200, 2, 10, 2147483647

                                    2015-10-16T13:15:01.338Z [FF8CD7E0 info 'ThreadPool'] Thread enlisted

                                    2015-10-16T13:15:01.341Z [FF8CD7E0 info 'Default'] Vmacore::InitSSL: handshakeTimeoutUs = 20000000

                                    2015-10-16T13:15:01.344Z [FF971B70 info 'Libs'] VThreadBase detected multiple threads.

                                    2015-10-16T13:15:01.344Z [FF971B70 warning 'Libs'] SSL_VerifyCbHelper: Certificate verification is disabled, so connection will proceed despite the error

                                    2015-10-16T13:15:01.344Z [FF971B70 warning 'Libs'] SSL_VerifyCbHelper: Certificate verification is disabled, so connection will proceed despite the error

                                    2015-10-16T13:15:01.344Z [FF971B70 warning 'Libs'] SSL_VerifyCbHelper: Certificate verification is disabled, so connection will proceed despite the error

                                    2015-10-16T13:15:01.365Z [FF971B70 warning 'Libs'] SSL_VerifyCbHelper: Certificate verification is disabled, so connection will proceed despite the error

                                    2015-10-16T13:15:01.365Z [FF971B70 warning 'Libs'] SSL_VerifyCbHelper: Certificate verification is disabled, so connection will proceed despite the error

                                    2015-10-16T13:15:01.366Z [FF971B70 warning 'Libs'] SSL_VerifyCbHelper: Certificate verification is disabled, so connection will proceed despite the error

                                    2015-10-16T13:15:01.386Z [FF8CD7E0 quiet 'Default'] Successfully acquired hardware: HP Compaq 8100 Elite SFF PC

                                    2015-10-16T13:15:01.536Z [FF9B2B70 info 'ThreadPool'] Thread delisted

                                    2015-10-16T13:15:01.536Z [FF8CD7E0 info 'ThreadPool'] Thread delisted

                                     

                                    ==> hostd.log <==

                                    2015-10-16T13:15:01.379Z [FFC40B70 verbose 'SoapAdapter'] Responded to service state request

                                     

                                    ==> rhttpproxy.log <==

                                    2015-10-16T13:15:01.343Z [FFAD3B70 verbose 'Proxy Req 00212'] New proxy client <io_obj p:0x1f053070, h:19, <TCP '127.0.0.1:80'>, <TCP '127.0.0.1:39646'>>

                                    2015-10-16T13:15:01.364Z [FFAD3B70 verbose 'Proxy Req 00213'] New proxy client <io_obj p:0xffb80790, h:21, <TCP '127.0.0.1:80'>, <TCP '127.0.0.1:38401'>>

                                     

                                    ==> syslog.log <==

                                    2015-10-16T13:15:01Z syslog[49229]: starting hostd probing.

                                    2015-10-16T13:15:01Z syslog[49229]: hostd probing is done.

                                     

                                    ==> vmkernel.log <==

                                    2015-10-16T13:15:01.544Z cpu1:48711)World: 14299: VC opID hostd-f309 maps to vmkernel opID acb6d3a1

                                     

                                     

                                     

                                     

                                    SO, it's looking like it might just be something with the certificate.  I'll try re-installing ESX and see if I can correct this.

                                    1 2 Previous Next