Skip to main content

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 will show the Developers Bar, at the bottom, go  to the Emulation Tab .
        If page is loading as Document Mode: EDGE then It will not Load.
        If the Document mode says 5, 7, 8 or 10 , then it will load the Client Integration plugin without any issue.

4)       Remove any previously created ovftool configuration file: 

        On Windows: Rename ovftool.cfg from "C:\Users\<username>\AppData\Roaming\VMware" 
        On Linux: Rename "ovftool_ssldb" file from the user's home directory (\root for the user root) 
5)       Remove previously created any ovftool settings file 

        On Windows: Rename .csp_ovftool_settings from "C:\Users\<username>\AppData\Roaming\VMware"
        On Linux: Rename ".csp_ovftool_settings" from the user's home directory (\root for the user root)



If you are using Google Chrome and above and facing same error. Please follow below steps to resolve the issue.

1)       Follow below VMware KB 2150215 (https://kb.vmware.com/kb/2150215)




Happy Sharing …J

Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

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