Error: “One or more exceptions have occurred – Internal Server Error” when moving or copying vApps across vCenters in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• When attempting to move or copy a vApp between vCenters in VMware Cloud Director, the operation fails with:
  
  “One or more exceptions have occurred – Internal Server Error”


• The failure occurs during the ImportVAppFromOvfActivity phase.
  
  
• Affected tasks show errors in the vCD UI and task details similar to the following:
  
  com.vmware.ssdc.library.exceptions.MultipleLMException: One or more exceptions have occurred -
Multiple Exceptions follow:
[com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Internal Server Error]


• Log errors may show:
  
  ImportVAppFromOvfActivity::prepareNetworkMappings: Unable to construct network mappings. The hosts in the specified resource pool do not have any virtual networks defined.


• The issue prevents vApp or VM migration from one vCenter-backed Provider VDC to another.

 

Environment

VMware Cloud Director 10.6.x

Cause

This issue can occur when the “none network” configuration used by VCD for unmanaged VMs is inconsistent or missing between vCenters.

The vc_none_network_name or vc_none_network_moref entries for one of the vCenters are empty or invalid in VCD’s internal mapping.

As a result, the ImportVAppFromOvfActivity::prepareNetworkMappings validation fails because no valid backing network is found.

Resolution

Perform the following validation steps to ensure that both vCenters used by VMware Cloud Director have valid and consistent “none network” configurations:

1. Verify vCenter registration in VCD
   
   In the Provider Portal, navigate to Resources > vCenters.
   
   Confirm that all associated vCenters display a Healthy connection and that inventory synchronization completes successfully.
   
   
2. Confirm presence of a “none network” in each vCenter
   
   In the vSphere Client, verify that each vCenter has a distributed port group intended to act as the none network (the network used for VMs not connected to an OrgVDC or vApp network).
   
   The exact name of this network may vary between environments, but it must exist and be accessible to all hosts used by the Provider VDC.
   
   
3. Validate VM connections
   
   Identify any VMs managed by VCD that are not connected to OrgVDC or vApp networks.
   
   Ensure these VMs are connected to the valid none network present in the same vCenter.
   
   
4. Resynchronize inventory
   
   From Resources > vCenters, select each vCenter and choose Synchronize Inventory.
   
   This action refreshes network mappings and ensures VCD has up-to-date references to the port groups and backing networks.
   
   
5. If inconsistencies remain
   
   Create a new distributed port group in vCenter to serve as the none network.
   
   Reattach any affected VMs to this new network.
   
   Re-run inventory synchronization in VCD so the new configuration is registered.
   
   
6. Re-test vApp move or copy operations
   
   Once both vCenters have valid network references, repeat the cross-vCenter vApp move or copy operation.
   
   The task should now complete successfully.