Unable to deploy VM from Content Library template with error: Error getting https://<FQDN_OF_VC>:443/cls/data/#####/example.ovf: – HTTP/1.1 404 Not Found
search cancel

Unable to deploy VM from Content Library template with error: Error getting https://<FQDN_OF_VC>:443/cls/data/#####/example.ovf: – HTTP/1.1 404 Not Found

book

Article ID: 421222

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 8.0

Issue/Introduction

  • Unable deploy VM from VM templates which is residing on content library with below error.

Failed to deploy OVF package. Cause: The object or item referred to could not be found. Resource inaccessible. Error getting https://Error getting https:/<FQDN_OF_VC>:443/cls/data/#####/example.ovf: HTTP/1.1 404 Not Found.

  • From /var/log/vmware/content-library/cls.log we see below error 
    YYYY-MM-DDThh:mm:ss.512+13:00 | DEBUG    | ##### | cls-simple-activity-22    | VdcsFutureResultCallback       | setting the future with value Info (com.vmware.vcenter.ovf.import_session.info) => {
        state = IMPORT_ERROR,
        progress = 0,
        fileTransferMode = <null>,
        files = [],
        errors = [OvfError (com.vmware.vcenter.ovf.ovf_error) => {
        category = SERVER,
        issues = <null>,
        name = <null>,
        value = <null>,
        message = <null>,
        error = ResourceInaccessible (com.vmware.vapi.std.errors.resource_inaccessible) => {
            messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
        id = com.vmware.ovfs.ovfs-main.ovfs.http_get_error_resource_inaccessible,
        defaultMessage = Resource inaccessible. https://Error getting https://<FQDN_OF_VC>:443/cls/data/#####/example.ovf: HTTP/1.1 404 Not Found,
        args = [https://Error getting https://<FQDN_OF_VC>:443/cls/data/#####/example.ovf: HTTP/1.1 404 Not Found],
        params = <null>,
        localized = <null>
            data = <null>,
            errorType = RESOURCE_INACCESSIBLE
     
    YYYY-MM-DDThh:mm:ss.Z | WARN | mjaw233m-17827-auto-dr8-h5: 70002569-55-ae-4e-23 | transferService-priority-pool-8-thread-95 | NfcHostSelectionStrategy | Unable to find a host for transfer
     
    com. vmware. vapi. std. errors. UnableToAllocateResource: UnableToAllocateResource (com. vmware. vapi. std. errors.unable_to_allocate_resource) => {
    messages = [LocalizableMessage (com. vmware. vapi. std. localizable_message) => (
    id = com. vmware. api. vcenter. files.nfc.tickets.datastore.unable_to_allocate_resource,
    defaultMessage = Could not find a host to initiate an NFC connection,
    args = (),
    params = <null>,
    localized = <null>
    }]
    data = <null>
    errorType = UNABLE_TO_ALLOCATE_RESOURCE
     
    at com. vmware. vapi. std.errors. UnableToAllocateResource. newInstance2 (UnableToAllocateResource. java: 194)
    at sun. reflect.GeneratedMethodAccessor1510. invoke (Unknown Source)
    sun. reflect. DelegatingMethodAccessor Impl. invoke (DelegatingMethodAccessor Impl. java: 43)
    at java. lang. reflect.Method. invoke (Method. java: 498)
    at com. vmware. vapi. internal.protocol.client.msg. json. JsonApiProvider$ResponseCallbackImpl. received (JsonApiProvider. java: 418)
    at com. vmware. vapi. internal.protocol. client.msg. json. JsonApiProvider$1. received (JsonApiProvider. java: 505)
    at com. vmware. vapi. internal.protocol. client. rpc.http.handle. BioStreamingResponseHandlingStrategy$ControllableTransport. resumeRead (BioStreamingResponseHandlingStrategy. java:MM6)
     
    YYYY-MM-DDThh:mm:mm.531+13:00 | WARN     | #### | transferService-priority-pool-8-thread-9700 | TransferItemImpl               | Session ###32, Item example.ovf: Rescheduled to run in 300 sec. due to: Source or destination hosts necessary for transfer are busy or not available, cannot transfer content for: ds:///vmfs/volumes/####-####//contentlib-######68/####330/example.ovf?serverId=####3c.
    YYYY-MM-DDThh:mm:ss.531+13:00 | DEBUG    | ##### | transferService-priority-pool-8-thread-9700 | TransferItemImpl               | Scheduling transfer item ####32/example.ovf, not done yet
    YYYY-MM-DDThh:mm:ss.531+13:00 | DEBUG    | ##### | transferService-priority-pool-8-thread-9700 | TransferItemImpl               | Scheduling transfer item ####32/example.ovf in session ####32 to be activated in about 300 seconds
    YYYY-MM-DDThh:mm:ss.532+13:00 | DEBUG    | ##### | transferService-priority-pool-8-thread-9700 | TransferItemImpl               | Scheduling transfer item ####32/example.nvram, not done yet
    YYYY-MM-DDThh:mm:ss.532+13:00 | INFO     | null  | transferService-pool-7-thread-24858         | TransferItemImpl               | Transfer of item example.nvram in session #####32 has been attempted 9 times.
    YYYY-MM-DDThh:mm:ss.532+13:00 | DEBUG    | ##### | transferService-pool-7-thread-24858 | TransferItemImpl               | Session #####32, Item example.nvram: source item ready for transfer
    YYYY-MM-DDThh:mm:ss.532+13:00 | DEBUG    | ##### | transferService-pool-7-thread-24858 | HttpServerEndpointImpl         | Served endpoint for #####32/example.nvram: Not ready
    YYYY-MM-DDThh:mm:ss.532+13:00 | DEBUG    | ##### | transferService-pool-7-thread-24858 | TransferItemImpl               | Session #####32, Item example.nvram, Target http:/: Target not ready, waiting for connection
 

Cause

This issue occurs when no suitable ESXi host is available to initiate an NFC (Network File Copy) connection during the OVF import process.

NFC transfer fails when:

  • Source or destination hosts required for the copy are unavailable or busy

  • Hosts are disconnected, powered off, or in maintenance mode

  • Hosts do not have valid access to the source or destination datastores

  • Host resources are exhausted, preventing selection for NFC transfer

As a result, the Content Library service is unable to retrieve the OVF or associated VMDK files, leading to HTTP 404 and resource inaccessible errors.

 

Resolution

  • Verify that all ESXi hosts connected to the Content Library datastore are:

    • Powered on

    • Connected

    • Not in maintenance mode

    • Not under excessive resource load

  • Refresh datastore connectivity:

    • Rescan storage adapters on all relevant hosts

    • Confirm the datastore is mounted and accessible on at least one suitable host

  • Validate host access:

    • Ensure both source and destination datastores are accessible to the same host(s)

    • Confirm there are sufficient CPU, memory, and network resources available

  • Retry the VM deployment from the Content Library after validating host and datastore availability.

 

Additional Information

  • NFC (Network File Copy) is used to transfer VMDK files between datastores during OVF deployment.

  • For non-VMDK files, Content Library streams data over HTTP directly to the datastore.

  • For VMDK files, vCenter must select a valid source and destination host pair with access to the respective datastores.

  • If no suitable host pair is found, the OVF import session fails with Resource Inaccessible and HTTP 404 errors.

 

Powered by Wolken Software