an Internal error occurred in the vSphere client… VMware update Manager



Quickie post on how to correct the An Internal Error Occurred In The vSphere Client for  VUM Plugin.


I have searched the web and came across several cases simil to this one but my own is some kind of wired case. maybe installation issue.

let go.

Go to C:\Program Files (x86)\VMware\Infrastructure\Update Manager

Locate and open vci-integrity.xml and replace it with the FQDN of your vCenter




You do the same on the Extension.xml file where you put the FQDN of your vCenter instead of the IP Address



There will be one thing worth checking is the Firewall between the two machines, in my case, I’ve had to allow the ports on the windows built-in firewall to have this problem solved afterwards.

have fun

Syslog Configuration on All Hosts – PowerCLI

It comes to times when you will be looking at changing a setting on hosts at once avoiding the clicks, in my case I had to change a setting for around 150+ hosts on 4 datacenters from 4 vCenters and this will take a heck of a time.

This is a quick way you can change and point your ESXi hosts to a syslog server using PowerCli.

This will configure your Syslog Server IP address or hostname, Open the Outbound Ports and also restart your syslog services,

Double check your configuration through this


In case you wanted to go through this manually, these are the commands needed

To open your firewall :

To configure your Syslog entries

You will have to restart your syslog services .

Finally this command will show you the config state of your Host or hosts


ESXi – Add disk and convert your Raid0 to Raid1 on HP Proliant Gen9:

This quick post will show how to add a disk to your array and convert your Raid0 disk to a Raid1 configuration without bringing your ESXi host offline.

This chap has all the commands listed on his blog which are worth checking.

This has been tested and implemented on a Proliant BL460C Gen9 and went without any issue, you have to check the commands below if you are using a different HP Hardware and/or consult your hardware provider about similar commands if you are using a different hardware build.

Change a directory to /opt/hp/hpssacli/bin

We will start by checking that the status of your Array is healthy by running

./hpssacli ctrl all show status


Check again the status of your Slot using

./hpssacli ctrl slot=0 logicaldrive all show status


This command will show you the drives you have on your controller and the Raid Level used (Fault Tolerance)

./hpssacli ctrl slot=0 logicaldrive all show details


We added a disk to the blade and run the command. /hpssacli ctrl all show config which now shows me that I have an unassigned disk


./hpssacli ctrl slot=0 modify rebuildpriority=high to start the job as a priority

Running ./hpssacli ctrl slot=0 Id 1 add drives=allunassigned will assign the drive to the slot you are about to work with and you need to know that the cache will be disabled during the rebuild


Disk 2 is now added to the Raid0 which will be converted to a Raid1 once the rebuild is done




Running this ./hpssacli ctrl slot=0 id 1 modify raid=1 will modify the Raid0 into 1 which believe me it took around 5 Hours to convert a 1.TB Raid0 to  Raid1




Have fun

cannot execute upgrade script on host > Take 2

while doing some maintenance on one of my ESX host and trying to bring it to the versions we currently use, I again came across this error which I’ve wrote about last time but following the fix suggested this again prevented me to upgrade my host to the version 5.5 U2 Build 3116895.

while investigating the vua.log, II ‘ve found this error “ ValueError: Cannot merge VIBs Mellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560, Mellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560 with unequal payloads attributes: ([net-mst: 8.250 KB], [net-mst: 8.242 KB])

why? According to VMware “This issue occurs because the update process detects two VIBs with same VIB ID and version, and attempts to merge from different sources, which can be either an online software depot, offline ZIP file or a VIB installed on the ESXi host with different values for stateless-ready attributes.”

here is the fix.

if you know which Nics are installed in your Host that’s great otherwise check using this command via SSH and see if your host is using them

~# esxcli network nic list

in my case I’m on Emulex FlexFabric



list All the VIBs drivers you have on your host

~# esxcli software vib list | grep net


from there you can remove the unused VIBS from your drivers repository and you should be good to go.

~# esxcli software vib remove -n net-mst

you will get


don’t forget to reboot your host once done.

Remediate entity Cannot execute upgrade script on host.

Spoke to soon on my last blog,

came back from lunch and here my upgrade didn’t work, this time I’m receiving Host upgrade from ESXi 5.5 to 6.0U1 Failed with the following error, Remediate entity Cannot  execute upgrade script on host.  with this error on VUM events


I do recall this problem again a while back which pointed me to a VMware KB  2007163 but this time it didn’t do the trick. went on the logs vua.log on my host and found this error below

2015-11-30T17:31:33.157Z error vua[FFC2B0D0] [Originator@6876 sub=Default] Alert:WARNING: This application is not using QuickExit(). The exit code will be set to 0.@ bora/vim/lib/vmacore/main/service.cpp:162
–> Backtrace:
–> [backtrace begin] product: VMware vSphere Update Manager Agent, version: 6.0.0, build: build-2621470, tag: vua

This seem odd to me, but looked around the net and found a solution thanks to this chap at

Put your machine into Maintenance mode, remove it from your cluster and then SSH to it and run the below.

cp /opt/vmware/uninstallers/ /tmp
chmod +x /tmp/


reboot and put this one back to your cluster.