3 Replies Latest reply on Oct 10, 2018 5:26 PM by sadatm01

    6.7 SSO

    kevonski Lurker

      I'm receiving this error during the vCenter 6.70a setup (the install screen goes to 80+% or so then):

      “Error

      Could not connect to VMware Directory Service via LDAP. Verify VMware Directory Service is running on the appropriate system and is reachable from this host.

      Resolution

      Please search of these symptoms in the VMware Knowledge Base for any known issues and possible workarounds. If none can be found, please collect a support bundle and open a support request. “

       

      I’ve also tried completing the operation via the web UI at https://host-IP:5480 to the same result.

      I used the default of vsphere.local for the SSO hostname.

      NTP and DNS are setup correctly. This is a new install of vCenter 6.70a on a new install of ESX 6.70a.

      “Getting Started - vCenter Server Appliance with an Embedded Platform Services Controller (PSC)

      This appliance cannot be used or repaired because a failure was encountered. You need to deploy a new appliance. Failure details “.

      Any help is appreciated!

       

      Kevin

        • 1. Re: 6.7 SSO
          qYIpBHAIzM Novice

          Hi Kevin.

           

          Hopefully you've solved the issue in the meantime, but this information might come in handy for others experiencing the same issue.

           

          I saw this same issue when trying to install vCenter (with embedded PCS) on my setup.

           

          What ultimately fixed it was when I created the reverse-lookup entry for the dns-entry.

           

          So if you haven't solved this yet, you should probably double-check your dns-setup.

           

          Br. Frank.

          1 person found this helpful
          • 2. Re: 6.7 SSO
            NeoAvalon Novice

            Creating a reverse lookup in DNS resolved this error for me as well- thanks!

            1 person found this helpful
            • 3. Re: 6.7 SSO
              sadatm01 Lurker

              Brilliant! had exactly the same issue and after creating reverse DNS lookup it has done the magic.