Lunetikk's IT Wiki

A host profile is attached by the cluster and there is no way to apply or remediate.

Reason:
It seems like you are using the HTML webclient which doesnt have this option (yet).

Fix:
Either use the flash version (if you have vCenter 6.0 the software client will also work)
or
apply it via PowerCLI

#remove everything after <vcenter> to use your windows authentication
Connect-VIServer <vcenter> -User <user> -Password <password>
Apply-VMHostProfile -Entity <esxhostname.your.domain>
 
#if you are not sure what name to use, just list all your esx hosts
(Get-VMHost).name

Recheck the compliance of the host profile. If some issues still exist, execute “Apply-VMHostProfile …” again.

Trying to activate vSphere HA fails with the following messages:

vSphere HA agent cannot be correctly installed or configured

Reconfigure vSphere HA host
Status: Operation timed out.

Reason:
There could be different reasons…

Fix:
At first, if you dont want to get VMs migrated right away, activate maintenance before executing something from below.

Check if your service “vSphere High Availability Agent” is running on your host. (its stopped by default if you are in maintenance mode)
If it isnt running, start it and execute “Reconfigure for vSphere HA”.

Still not working? alright then…

Go to your cluster configuration and select “Services → vSphere Availability”
On the right side of “vSphere HA is Turned ON” click edit and turn it off.
Apply and then turn it back on.

Your vSphere should now work again.

If it still doesnt, www.giyf.com

Trying to search a system fails with the following message:

Login to the query service failed.


The server could not interpret the communication from the client. (The remote server returned an error: (500) Internal Server Error.)

Reason:
VMware says that this is “an expected behavior”

Searching for Inventory objects when logged in to the vSphere Client using the Use Windows session credentials option is not supported.

For sure this is expected… why would you let lazy people search in your vCenter?

Fix:
At the login screen deselect “Use Windows session credentials” and log in with your username and password.

https://kb.vmware.com/s/article/2143566

Connecting a backed up VMDK to the same machine results in a duplicated UUID

msg.disk.duplicateUUID:Virtual disks

"/vmfs/volumes/DATASTORE/VM_FOLDER/VM_NAME.vmdk" and "/vmfs/volumes/DATASTORE/VM_FOLDER/VM_NAME2.vmdk" have the same UUID. Virtual disks with the same UUID should not be assigned to a virtual machine because duplications can lead to problems when the guest boots. Make sure the virtual disks have unique UUIDs.

Reason:
Well… Duplicated UUIDs…

Fix:
Login on the ESX host to change the UUID of the VMDK.
Check the current and set a new one afterwards.

vmkfstools -J getuuid <vmname>.vmdk
vmkfstools -J setuuid <vmname>.vmdk

https://kb.vmware.com/s/article/2006865

Creating / removing a snapshot fails with the following message

Cannot create snapshot
Operation not allowed in current state

On the ESX itself you may find the following error in /var/log/hostd.log

2019-10-08T07:16:52.016Z error hostd[14B81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/acde0a05-cd36531b/VMNAME/VMNAME.vmx] Invalid transition requested (VM_STATE_ON_SHUTTING_DOWN -> VM_STATE_CREATE_SCREENSHOT): Invalid state

[07:43:03.404 F64A8B90 error 'vm:/vmfs/volumes/4acc704a-2b59540f-116b-0017a477fc18/VMNAME/VMNAME.vmx'] Invalid transition requested (VM_STATE_ON_SHUTTING_DOWN -> VM_STATE_CREATE_SNAPSHOT): Invalid state

Reason:

This issue occurs if the vCenter Server management agents have stopped causing the snapshot attempt to move in to the ON_SHUTTING_DOWN state.

Fix:

Connect to your ESX host via ssh and restart the management agents

/etc/init.d/hostd restart
/etc/init.d/vpxa restart

You should be able to create or remove the snapshot afterwards

https://kb.vmware.com/s/article/1027707