6 Replies Latest reply on Oct 17, 2019 12:13 AM by Blanton1F

    Upgrading vCenter server 6.5 to 6.7

    AlInOz Lurker

      Hi all,

       

      Here's my scenario:

       

      I have two VMWare ESX hosts in a cluster connected to a storage array with all the required licensing for vMotion etc..  This is managed by a vCenter Server Essentials server installed on a standalone ESXi server using a free license.  The reason for this is to have the management outside of the cluster.

       

      I want to upgrade the vCenter server to 6.7, but get the following error during the upgrade process: VCHA is not enabled on the source host.

       

      Short of copying the appliance onto my VMWare cluster to do the upgrade, is there a way of getting around this without me having to copy the appliance?

        • 1. Re: Upgrading vCenter server 6.5 to 6.7
          a.p. Guru
          Community WarriorsUser ModeratorsvExpert

          Welcome to the Community,

           

          Please check whether resetting the root password helps.

          see e.g. https://martinsblog.dk/vcenter-server-appliance-6-7-upgrade-a-problem-occurred-while-getting-data-from-the-source-vcente…

           

          André

          • 2. Re: Upgrading vCenter server 6.5 to 6.7
            AlInOz Lurker

            Hey André

             

            Reset password, but same issue.  I'm guessing its because it wants to do a VMotion to the new migrated vCenter server once done.

             

            Excerpt from log:

             

            2018-12-18T06:14:18.952Z - info: VM with hostName vcenter.grc.local: { _type: 'VirtualMachine',

              _moid: '1',

              config: { template: false },

              guest:

               { hostName: 'vcenter.grc.local',

                 ipAddress: '192.168.4.38',

                 net: [ [Object] ] },

              name: 'VMware vCenter Server Appliance',

              summary:

               { storage:

                  { committed: 173772122777,

                    uncommitted: 7374,

                    unshared: 173772122777,

                    timestamp: 2018-05-19T16:21:23.857Z } } }

            2018-12-18T06:14:18.953Z - info: VM Identifier for Source VC: 1

            2018-12-18T06:14:19.004Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Current license or ESXi version prohibits execution of the requested operation.

            2018-12-18T06:14:19.004Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Current license or ESXi version prohibits execution of the requested operation.

            2018-12-18T06:14:19.004Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Current license or ESXi version prohibits execution of the requested operation.

            2018-12-18T06:14:19.004Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Current license or ESXi version prohibits execution of the requested operation.

            2018-12-18T06:14:19.004Z - error: Failed to read the nodetype, Error: Current license or ESXi version prohibits execution of the requested operation.

            2018-12-18T06:14:19.005Z - info: Checking if password expired

            2018-12-18T06:14:20.230Z - info: Banner from server,

            VMware vCenter Server Appliance 6.5.0.14000

             

             

            Type: vCenter Server with an embedded Platform Services Controller

             

             

             

             

            2018-12-18T06:14:20.231Z - info: Connection ready

            2018-12-18T06:14:20.244Z - info: STDOUT: Last login: Tue Dec 18 13:25:33 2018 from 192.168.4.119

             

             

             

             

            2018-12-18T06:14:20.244Z - info: STDOUT: date

            exit

             

             

            2018-12-18T06:14:20.513Z - info: STDOUT: Connected to service

             

             

            2018-12-18T06:14:20.523Z - info: STDOUT:

                * List APIs: "help api list"

                * List Plugins: "help pi list"

                * Launch BASH: "shell"

             

             

             

             

            2018-12-18T06:14:20.525Z - info: STDOUT: Command>

            2018-12-18T06:14:20.526Z - info: STDOUT: dat

            2018-12-18T06:14:20.527Z - info: STDOUT: e

             

             

            2018-12-18T06:14:20.538Z - info: STDOUT: Unknown command: `date'

             

             

            2018-12-18T06:14:20.538Z - info: STDOUT: Command> ex

            2018-12-18T06:14:20.538Z - info: STDOUT: it

             

             

            2018-12-18T06:14:20.581Z - info: Stream :: close

            2018-12-18T06:14:20.581Z - info: Password not expired

            2018-12-18T06:14:20.583Z - error: sourcePrecheck: error in getting source Info: ServerFaultCode: Current license or ESXi version prohibits execution of the requested operation.

            2018-12-18T06:14:20.583Z - info: VCHA is not enabled on the source host

            2018-12-18T06:14:31.734Z - info: Log file was saved at: \\tsclient\aj\Downloads\installer-20181218-155759822.log

            • 3. Re: Upgrading vCenter server 6.5 to 6.7
              MikeStoica Expert
              vExpert

              From your logs, looks like this is the issue: Current license or ESXi version prohibits execution of the requested operation.

              • 4. Re: Upgrading vCenter server 6.5 to 6.7
                a.p. Guru
                User ModeratorsCommunity WarriorsvExpert

                Not sure whether this is caused by the free Hypervisor license on the standalone host!?

                Since you only have two hosts in the cluster, you may try to - at least temporarily - assign the third Essentials (Plus) license to the standalone host.

                 

                André

                • 5. Re: Upgrading vCenter server 6.5 to 6.7
                  AlInOz Lurker

                  Yeah, figured the free ESXi license was causing the issue.

                   

                  I eventually decided to trash the vCenter Server 6.5 appliance and install a new 6.7 vCenter Server appliance and connect the two hosts to the new server.  Checked all configs and tested VMotion and auto failover and all works fine.

                   

                  The vCenter Server 6.7 appliance install was another story on its own.  Ended up having to upgrade the standalone 6.5 vSphere server to 6.7 before the installation would complete the 2nd stage, otherwise it was just crashing out early in stage 2.

                  • 6. Re: Upgrading vCenter server 6.5 to 6.7
                    Blanton1F Lurker

                    You can also have external Platform service controllers (PSC)

                    Hi all,

                     

                    Here's my scenario:

                     

                    I have two VMWare ESX hosts in a cluster connected to a storage array with all the required licensing for vMotion etc. This is managed by a vCenter Server Essentials server installed on a standalone ESXi server using a free license. The reason for this is to have the management outside of the cluster.

                     

                    I want to upgrade the vCenter server to 6.7, but get the following error during the upgrade process: VCHA is not enabled on the source host.

                     

                    Short of copying the appliance onto my VMWare cluster to do the upgrade, KrogerFeedback is there a way of getting around this without me having to copy the appliance?