OVA/OVF deployment fails with “The OVF Descriptor Is Not Available”
Article ID: 418565
Updated On:
Products
Issue/Introduction
When importing an OVA in vCenter, the deployment fails with the error,
Transfer failed: The OVF descriptor is not available.
In the ESXi host log /var/log/vmware/content-library/cls.log, entries similar to the following appear,
YYYY-MM-DDTHH:mm:ss.xxxZ | DEBUG | ############################################# | cls-simple-activity-# | ImportSessionActivity | Session is in state IMPORT_OVF_TRANSFER
YYYY-MM-DDTHH:mm:ss.xxxZ | DEBUG | ############################################# | cls-simple-activity-# | ImportSessionActivity | OVF descriptor not available yet for session <UUID>
YYYY-MM-DDTHH:mm:ss.xxxZ | ERROR | ############################################# | cls-simple-activity-# | ImportSessionActivity | Transfer failed, couldnt transfer OVF descriptor, or manifest, or cert.
YYYY-MM-DDTHH:mm:ss.xxxZ | ERROR | ############################################# | cls-simple-activity-# | ImportSessionActivity | OVF import session <UUID> failed with server error.
com.vmware.vapi.std.errors.ServiceUnavailable: ServiceUnavailable (com.vmware.vapi.std.errors.service_unavailable) => {
messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
id = com.vmware.ovfs.ovfs-main.ovfs.transfer_failed_ovf_unavailable,
defaultMessage = Transfer failed: The OVF descriptor is not available.,
args = [],
params = <null>,
localized = <null>
}],
data = <null>,
errorType = SERVICE_UNAVAILABLE
Restarting the following components did not resolve the issue:
-
vmware-content-library service
-
vCenter Server itself
All vCenter certificates were verified and none of them are expired.
Environment
-
vCenter Server 8.0, 9.0
-
ESXi 8.0, 9.0
-
OVA imported through the vSphere Client (UI)
-
OVA upload performed from an administrator’s workstation
-
Content library involved in the upload process
-
ESXi hosts reachable from vCenter, but upload path depends on workstation → ESXi communication
Cause
The OVA/OVF upload path requires direct communication between the workstation performing the import and the destination ESXi host. Even though the operation is initiated through vCenter, the actual file upload (including the OVF descriptor) is sent from the client machine directly to the ESXi host. If this connection is blocked, incomplete, or interrupted, the ESXi host cannot receive the OVF descriptor, causing the import session to fail.
Common reasons include:
- Workstation cannot reach the ESXi host on TCP 443 (HTTPS upload)
- Workstation cannot reach the ESXi host on TCP 902 (NFC data transfer)
- Firewall/VPN/proxy restricting outgoing connections
- Deploying from a remote network segment with limited access
Because the root cause is network path from client → ESXi, restarting vCenter or its content-library service has no effect.
Resolution
1. Verify connectivity from the workstation to the ESXi host
From the administrator’s machine, ensure the two ports 443 and 902 on the ESXi host are reachable.
2. Try deploying the OVA from another workstation
Use a workstation that Is in the same VLAN/subnet as the ESXi management network and/or has unrestricted network access to the ESXi host.
3. Retry the OVA import after confirming connectivity
Once the workstation can directly reach the ESXi host on the required ports, repeat the OVA deployment. The import should proceed normally and the OVF descriptor will be transferred successfully.
Feedback
