Error: "Unexpected VMware Cloud Director error" when recreating a replication in VMware Cloud Director Availability

Products

• VMware Cloud Director
• VMware Cloud Director Availability - Disaster Recovery 4.x
• VMware Cloud Director Availability - Migration 4.x

Issue/Introduction

• Creating a new protection or migration fails with an error similar to the following:
  
  Unexpected VMware Cloud Director error. [ UI-########-####-####-####-############-####-##-########-####-####-####-############ ] class java.lang.NullPointerException
  
  
• May also see similar errors in the destination Cloud Director Debug Logs:
  
  LinkVMsToTargetVAppActivity    | [Activity Execution] Serializing Future: constituteNetVmFuture-> ActivityFutureTask [activityExecutionState=AbstractActivityExecutionState [activityName=com.vmware.vcloud.fabric.net.activities.ConstituteNetworkedVmActivity, clientURI=urn:uuid:########-####-####-####-############, entityURI=urn:uuid:########-####-####-####-############, currentPhase=com.vmware.vcloud.fabric.net.activities.ConstituteNetworkedVmActivity$SynchronizeNetworkedVmNicsPhase, cancelRequested=false, parameters(size)=#], exception=java.util.concurrent.ExecutionException: com.vmware.ssdc.library.exceptions.InventoryObjectNotFoundException: Could not find object with moref "vm-####" and VC ID "########-####-####-####-############" in inventory category "VirtualMachine".
• The VM was previously protected, but that protection has been deleted from VCDA.

Environment

VMware Cloud Director Availability 4.7.3.x

Cause

Stale entries for the old RTVM still exist in the VMware Cloud Director database, which is often caused by the previous removal of a replication that did not successfully clear from the destination VCD. VCD is attempting to attach the old RTVM using the stale vmmoref from the database, which no longer exists in the destination vCenter Server.

Resolution

The stale database records will need to be reviewed and removed. As database modifications is necessary to resolve this issue, please open a Support Request with VMware Technical Support and reference this KB article (425139) to remediate.