An additional note, I had uploaded the ISO file into the Content Library I had created and attached to the VCSA VM to perform the update. When I tried to disassociate the CDROM (mounting point for the ISO) from the VCSA VM after the update, this is when all my problems started.
When you get that error message, is the ISO still mounted? Can you show the config of the vCSA from the ESXi host client?
No, the ISO is no longer mounted, which is where I believe my problem stems. I can edit the config of the VCSA from the ESXi host client but I continue to receive the same error message and will not allow me to make any changes.
I was thinking about removing the VCSA VM from the inventory via the ESXi Command Line and trying to re-add, but not sure that is a viable solution.
So can you show the config? Look at events when powering on and show what's logged there as well, please.
Show config, do you mean view the vmx config file?
In the Events log there are two entries:
1. VCSA on ESXi07.domain.name host in ha-datacenter is resumed <------ my ESXi host is joined to a domain
2. Issue detected for VCSA on ESXi07.domain.name host in ha-datacenter: Configuration file has unexpected changes. Virtual machine has been terminated. Unregister and re-register virtual machine if the configuration file is correct.
1 person found this helpful
I was thinking about removing the VCSA VM from the inventory via the ESXi Command Line and trying to re-add, but not sure that is a viable solution..
Instead of doing this, it might be worth to try reloading the VM from the command line. see https://kb.vmware.com/s/article/1026043
Reload first as André mentions. If it still won't start, show the VM's configuration.
Attempted to reload the VM and received the following error:
faultCause = (vmodl.MethodFault) null,
faultMessage = <unset>,
reason = "Infalid fault"
msg = "Received SOAP response fault from [<cs p:03c88708, TCP:localhost:80>]: reload
My vCenter is not connected to the internet so I will copy and post the VCSA VM config file contents here shortly.
I've been trying to download your file, but I keep get timeouts and failures. It's probably due to the forums. Can you paste a screenshot? Also, what is the output from the following command via ESXi shell or SSH:
esxcli software vib list | grep esx-ui
daphnissov and a.p.,
Thank you for all your guidance and assistance with this issue.
I proceeded to Unregister the VCSA VM from the ESXi host and re-Register VM through the datastore and VCSA came back up. I was able to log back into the vsphere web client and verifying all is good. The update held (checked via the VAMI web interface) and through the VCSA console but unsure what the hang up was with ISO.
I did read somewhere that HA may have been the culprit, which I had enabled during the update. Can you all confirm that may have been the case??