Skip to main content


Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine. We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing. On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state. Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds. Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more

Unable to upload and download images or OVF into vCloud director

Recently I got an issue from one of my customer where they were unable to upload or download the files from vCloud Director. At the time or upload or download files into catalog, its prompting below error and ask for download the Client integration plugin, even though the CIP is already installed into the machine from where we are trying to upload the image into Vcd. “The Client integration Plugin-in must be installed to enable OVF upload and download functionality. Click the link below to download installer. When the download has completed, you must close your browser before you can install the plugin” To resolve the issue we have followed below steps. If you are using Internet Explorer 11 and above and facing same error. Please follow below steps to resolve the issue. 1)        Make sure your VCD FQDN is listed into trusted site. 2)        Enable Compatibility mode. 3)        When you load vCloud Director into Internet Explorer, press F12 and it w

Shockwave Flash crashes on vSphere web application

Recently there were an issue where vSphere Web client stopped working with Google crome and Firefox. After login to vSphere webclient or any other web based VMware application getting error where its states “ Shockwave Flash has crashed” After investigating it’s been found that the google recently published a newer version of Flash( with its latest update of crome ( 61.0.3163.100). However, the newer version of Flash was not available for download or listed in Adobe site. Same issue identified on the Firefox where the latest Flash were causing the same issue. Workaround identified 1) One-way to disable the auto-update feature of Chrome, you can do so by changing the following  HKLM\SOFTWARE\Policies\Google\Update\AutoUpdateCheckPeriodMinutes  to 0 2) It looks like you can also simply replace the new pepperflash DLL with an older version and placing it within the folder (in case Chrome tries to update it). If y

Failed to lock the file - Continue...

In our day to day operational activity into the vCenter we usually encounter with issue, like unable to power on the VM. VM failed to lock the file or file has been locked. To resolve the issue, I have some very usefull command which you can execute to immediatly idently where the .vmdk is being locked. As most of you know that vmkfstools -D is used to identify the lock on the .vmdk  where its gives the mac address of the VM or Host where the lock exist and we can identify the lock from Esxcli. ie (vmkfstools -D /vmfs/volumes/abcd.vmdk) Apart from this there is one beautiful command which we can use to identify the lock on the .vmdk. The command to identify the lock is "vmkfsfilelockinfo -p (location of .vmdk) vmfsfilelockinfo -p (/vmfs/volumes….) You see ouput similar to: vmfsflelockinfo Version 1.0 Looking for lock owners on "VM1_1-000001-delta.vmdk" "VM1_1-000001-delta.vmdk" is locked in Exclusive mode by host having mac address

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl

Installing vCenter Appliance 6.5

vCenter appliance 6.5 is one of the latest & stable release of vCenter . vSphere 6.5 adds an X-Large deployment size, the update manager and a fully supported migration assistant to the appliance. So it’s time to migrate your Windows based vCenters to appliance with vSphere 6.5. vSphere 6.5 is fully dependent on webclient. So no more vSphere client or C# client. VCSA 6.5 Enhancements Supports up to 2000 ESXi Hosts and 35.000 Virtual Machines Guided Installer (Interactive Installer, instead of OVF Template) Robust deployment (Separate Deployment and Configuration to prevent failed deployments Migration Assistant (Migrate vCenter Server 5.5 or 6.0 for Windows to vCenter Server Appliance) Native High Availability VMware Update Manager Built-In Backup+Restore Improved Appliance Management HTML5-based vSphere Client Photon OS (Replaces SUSE Enterprise 11) Compatibility  To view the compatibility of Esxi,