Error: Transfer failed: The OVF descriptor is not available
Article ID: 418565
Updated On:
Products
Issue/Introduction
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.x, 9.x
ESXi 8.x, 9.x
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
- The vmware-content-library service in vCenter terminates the import session abnormally.
Because the root cause is network path from client → ESXi, restarting vCenter or its content-library service has no effect.
Resolution
- Restart vCenter Services: Log in to the vCenter Server Appliance (VCSA) via SSH and restart the content library service:
service-control --restart vmware-content-library - Verify Network Connectivity: Ensure the workstation can reach the destination ESXi host directly on ports 443 and 902. Use a jump box in the same management VLAN if necessary.
- Check Certificates: Confirm that vCenter Server certificates are valid and not expired.
- Retry Deployment: Redeploy the OVA template through the vSphere Client after verifying service status.
Feedback
