If you are experiencing issues uploading vApps or media to catalogs, here are some steps to try and gather additional information about the problem.
If the vApp or media appears to upload in full and then fails (or appears to be successful but later an error is reported), check the logs on the VCD cell ($VCLOUD_HOME/logs/vcloud-container-debug.log).
If the transfer dialog fails to appear or the upload appears to fail, you'll want to troubleshoot from the client-side of the connection.
Verify that you have version 1.6.0 or higher of the Java plug-in installed on your system. With Firefox you can type about:plugins in the Location bar to see what plug-ins are installed. You can also go to http://javatester.org/version.html to see what version is reported. The transfer applet requires 1.6.0 or higher, and 1.6.0 update 10 or newer is strongly recommended. If you don't have the correct version visit http://java.com/en/download/index.jsp to install it
Try enabling the Java console and logging so you can trace what's going on with your upload. To do this, open the Java control panel. On Windows this may be accessed via Start > Control Panel > Java. On Linux you'll typically need to look for /usr/bin/ControlPanel or $JAVA_HOME/jre/bin/ControlPanel
Click on the Advanced tab
Expand the Java console option and select Show console. This will allow you to view the logs as the transfer happens
Expand the Debugging option and check all three options (Enable tracing, Enabling logging, Show applet lifecycle exceptions).
Click the OK button to save the changes and close the Java control panel
Restart your browser and reattempt the file transfer
This time the Java console window should open as the applet is loaded and debugging information will be printed to the console, hopefully revealing the cause of the problem
If the Java console does not appear, verify the steps above were performed properly.
When the problem is resolved you may want to undo the changes you made in the Java control panel in order to hide the console once again and to disable/lower the logging level.
Attempting to upload an older version 0.9 OVF that is not supported by VCD. VCD requires OVF 1.0 or 1.1.
Attempting to upload an OVF that fails to pass the security filters in VCD. This can happen if the OVF:
Has a file reference that refers to a non-local disk (e.g. an HTTP URL)
Has a file reference that contains spaces in the file name
Has a file reference that uses absolute file paths or attempts to access a parent directory using ".."