Deploying an OVA/OVF with the vSphere Client fails at 99%

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

This article provides steps to work around the issue when deploying an OVA/OVF with the vSphere Client fails at 99%.

Symptoms:

• Deploying an .ova with vSphere Client fails at 99%
• You see the error:
  
  Failed to deploy OVF package: The request was aborted: The request was canceled
   
• The status of the failed deploy task is:
  
  The task was canceled by a user
   
• The hostd logs contain errors similar to:
  
  error 'HttpNfcSvc'] [DiskUploadWorker] Stream reader initialization failed.
  warning 'Proxysvc Req?????'] The client closed the stream with a request not fully forwarded.
  info 'Vmomi' opID=A1B8F604-0000009C] Activation [N5Vmomi10ActivationE:0x5d869cc0] : Invoking [abort] on [vim.HttpNfcLease:session[5237eee5-c5ec-0cbe-1632-e27303ee219b]52b52f27-d9eb-2520-c757-f704f62a0e20]
   

  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment. 　

Environment

VMware vCenter Server 5.5.x
VMware vCenter Server 4.1.x

Cause

This issue can occur if the OVF's .cert file is a multiple of 1024 bytes. This is only visible after the .ova is untarred.

 

This also occurs if the OVF package is corrupt or incomplete.

Resolution

Verify if the package size of the OVF is correct. Download again if required. If the package is correct, follow the workaround.

To work around this issue, use any one of these options:

• Deploy the .ova with the Open Virtualization Format Tool
• Unpack the .ova and deploy the .ovf with the vSphere Client
• Deploy the .ova from a URL

Additional Information

For more information on how to create and deploy OVA/OVFs, see the Datacenter Administration Guide.