Skip to main content

Migration pre check fails,Internal error occurs during VMware vCenter Inventory Service pre-upgrade checks

 Symptoms

When migrating the vcenter from 6.5 to 6.7 ,the pre checks fails with error

migration-assistant-16046470| I: ParseErrorsWarningsFromPreUpgradeOutput: Error messages: Error: Internal error occurs during VMware vCenter Inventory Service pre-upgrade checks.

In the collection requirement logs for invsvc:

2020-07-08T10:57:23.144Z INFO service_manager Parsing service status The specified service does not exist as an installed service.^M
2020-07-08T10:57:23.144Z ERROR __main__ Upgrade Phase 'is:CollectRequirements' failed. Exception: Service 'vpxd-svcs' does not exist.^M
Traceback (most recent call last):^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\payload\componentPhaseLauncher.py", line 461, in main^M
    executionResult = systemExtension(exeContext)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\extensions.py", line 94, in __call__^M
    result = self.extension(*args)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\extensions.py", line 110, in _func^M
    return func(*args)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\is\__init__.py", line 61, in doCollectRequirements^M
    return is_upgrade.collectRequirements(context)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\extensions.py", line 110, in _func^M
    return func(*args)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts\is\is_upgrade_600.py", line 145, in collectRequirements^M
    isStatus = serviceManager.getStatus(isserviceName)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\service_manager.py", line 979, in wrapper^M
    return getattr(controller, attr)(*args, **kwargs)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\service_manager.py", line 812, in getStatus^M
    status = self.__getStatus(serviceName, statusParser or self.statusParser)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\service_manager.py", line 693, in __getStatus^M
    status = statusParser.parse(cmdResult, serviceName)^M
  File "C:\mig156A.tmp\PFiles\VMware\CIS\cis_upgrade_runner\libs\sdk\service_manager.py", line 245, in parse^M
    raise IllegalServiceError("Service '%s' does not exist." % (serviceName))^M
IllegalServiceError: Service 'vpxd-svcs' does not exist.^M
Cause
This happens in case the service-control file on the source vcenter machine is corrupt or blank

If you run the service-control command it will either give a traceback or no output at all
Impact / Risks
pre checks fails stating IllegalServiceError: Service 'vpxd-svcs' does not exist.
Resolution
Replace the service-control file from a working environment (lab) on the source vCenter
Test if the service-control --status --all gives expected output

Re run the migration assistant

Comments

Popular posts from this blog

Troubleshooting vpxd service on Windows vCenter Server

  Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue.   Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it.   Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...