Upgrade fails with error : "A problem occurred while getting data from the source vCenter Server" on Stage1
search cancel

Upgrade fails with error : "A problem occurred while getting data from the source vCenter Server" on Stage1

book

Article ID: 315462

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

vCenter upgrade fails with error at Stage 1 
Error : A problem occurred while getting data from the source vCenter Server

UI Installer Log

YYYY-MM-DDTHH:MM:SS.631Z - debug: token:undefined, length:9, running total:9
YYYY-MM-DDTHH:MM:SS.632Z - debug: vm found by IP: XX.XX.XX.XX
YYYY-MM-DDTHH:MM:SS.633Z - info: VM with hostName vcenter.fqdn: {
  _type: 'VirtualMachine',
  _moid: '33',
  config: { template: false },
  guest: {
    hostName: 'VCFQDN',
    ipAddress: 'XX.XX.XX.XX',
    net: [ [Object] ]
  },
  name: 'INDCVC01',
  parent: { value: 'ha-folder-vm', type: 'Folder' },
  runtime: { host: { value: 'ha-host', type: 'HostSystem' } },
  summary: {
    storage: {
      committed: 133813134839,
      uncommitted: 226906611517,
      unshared: 133813134839,
      timestamp: 2022-09-19T12:33:00.586Z
    }
  }
}
YYYY-MM-DDTHH:MM:SS.633Z - info: VM Identifier for Source VC: 33
YYYY-MM-DDTHH:MM:SS.694Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: A general system error occurred: vix error codes = (3017, 0).


As per the installer log, we are getting VIX ERROR 3017,0

Source node vmware.log

YYYY-MM-DDTHH:MM:SS.681Z| vmx| I125: VigorTransportProcessClientPayload: opID=8627aa9a seq=1768: Receiving GuestOps.InitiateFileTransferFromGuest request.
YYYY-MM-DDTHH:MM:SS.681Z| vmx| I125: Vix: [guestOps.c:778]: GuestOpsCredentialForGuest: All guest commands are disabled.
YYYY-MM-DDTHH:MM:SS.681Z| vmx| I125: Vix: [guestOps.c:779]: Error VIX_E_GUEST_OPERATIONS_PROHIBITED in GuestOpsCredentialForGuest(): Guest operations are not allowed on this virtual machine
YYYY-MM-DDTHH:MM:SS.681Z| vmx| I125: VigorTransport_ServerSendResponse opID=8627aa9a seq=1768: Completed GuestOps request with messages.

hostd log

YYYY-MM-DDTHH:MM:SS.683Z info hostd[2489201] [Originator@6876 sub=Hbrsvc] Replicator: powerstate change VM: 33 Old: 1 New: 1
YYYY-MM-DDTHH:MM:SS.684Z info hostd[2100503] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/600f7831-54e742f0-3d5c-d4f5ef05bbb0/VMNAME/VMNAME.vmx] [N8Guestsvc40InitiateFileTransferFromGuestRequestImplE:0x000000fd0cbd3d50] opCode=16 auth=<hidden> guestFilePath=/etc/vmware/deployment.node.type failed
YYYY-MM-DDTHH:MM:SS.684Z info hostd[2100503] [Originator@6876 sub=Solo.Vmomi] Activation [N5Vmomi10ActivationE:0x000000fd0c7f2cf0] : Invoke done [initiateFileTransferFromGuest] on [vim.vm.guest.FileManager:ha-guest-operations-file-manager]
YYYY-MM-DDTHH:MM:SS.684Z verbose hostd[2100503] [Originator@6876 sub=Solo.Vmomi] Arg vm:
--> 'vim.VirtualMachine:33'
YYYY-MM-DDTHH:MM:SS.684Z verbose hostd[2100503] [Originator@6876 sub=Solo.Vmomi] Arg auth:
--> (vim.vm.guest.NamePasswordAuthentication) {
-->    interactiveSession = false,
-->    username = "root",
-->    password = (not shown)
--> }

 

Cause

From the logs its clear that Guest Operations are disabled on the VMs. 

Resolution

To fix the VIX ERROR : 3017, 0
Check the source ESXi host /etc/vmware/config

[root@XXXXXX:~] cat /etc/vmware/config
libdir = "/usr/lib/vmware"
authd.proxy.nfc = "vmware-hostd:ha-nfc"
authd.proxy.nfcssl = "vmware-hostd:ha-nfcssl"
authd.proxy.vpxa-nfcssl = "vmware-vpxa:vpxa-nfcssl"
authd.proxy.vpxa-nfc = "vmware-vpxa:vpxa-nfc"
authd.fullpath = "/sbin/authd"
guest.commands.enabled ="false"

As we can see, Guest Operations are disabled.

To resolve this issue we need to remove this entry (guest.commands.enabled ="false") from from config and reboot the host. And try to perform the upgrade. 


Additional Information

Some customer's may have enabled this feature for security hardening. 
If we get VIX ERROR : 3017, 0 for any VM  and customer do not want to disable this feature then we can add the following parameter in VMX file to override the host level settings. 

Power off the VM
Edit VMX and add 
“guest.commands.enabled= "TRUE"”
Save the file and reload VM. 


But for upgrade scenario its good to remove the parameter from host config as the upgrade will deploy new VM and if guest operation is disabled at host level then upgrade will fail later as the guest operations will be disabled on the newly installed node.