Unable to protect VM -Error "Received unexpected exception from multi-site operation. The object 'vim.Task:dr.multiSiteOperation.MultiSiteOperationManager.startRemoteOperation' has already been deleted or has not been completely created.

Products

• VMware Live Recovery

Issue/Introduction

Unable to successfully protect the virtual machine using Array-Based Replication.

During the VM protection workflow, the operation fails and returns an internal error indicating an unexpected exception during the multi-site operation. Specifically, the task associated with initiating the remote operation appears to have been deleted or was not fully created at the time of execution, causing the protection process to terminate.

"ERROR
Operation Failed Internal error: Received unexpected exception from multi-site operation. The object 'vim.Task:dr.multiSiteOperation.MultiSiteOperationManager.startRemoteOperation' has already been deleted or has not been completely created
Operation ID:XXXXXXXXXX"

Environment

Array Based Replication.

VMware Live Site Recovery 9.x

 

Cause

In the SRM appliance navigate to below log location 
/var/log/vmware/srm/vmware-dr.log shows below traces - 

2025-12-01T12:42:09.172+01:00 verbose vmware-dr[134080] [SRM@6876 sub=StorageProvider opID=1246b7c0] GetStretchInfo requested for VM 'vim.VirtualMachine:vm-50033' with datastores [].
2025-12-01T12:42:09.172+01:00 verbose vmware-dr[134080] [SRM@6876 sub=StorageProvider opID=1246b7c0] DeviceGroupInfo for VM 'vim.VirtualMachine:vm-50033' is not available.Defaulting isCgStretched to false
2025-12-01T12:42:09.172+01:00 verbose vmware-dr[134593] [SRM@6876 sub=Replication opID=1246b7c0] [ProtectVms::PrepareProviderDone] Allocating database connection for VM vm-50033
2025-12-01T12:42:09.173+01:00 verbose vmware-dr[134098] [SRM@6876 sub=Replication opID=1246b7c0] [ProtectVms::PrepareConnectionAllocated] Instructing the provider to persist information regarding protection of VM vm-50033
2025-12-01T12:42:09.173+01:00 verbose vmware-dr[134098] [SRM@6876 sub=StorageProvider opID=1246b7c0] ProtectVmPreparePersist: group 'vm-protection-group-xxxxxxx:DPG, VM 'protected-vm-xxxx:a314-7096-6337:false'
2025-12-01T12:42:09.173+01:00 verbose vmware-dr[134098] [SRM@6876 sub=Replication opID=1246b7c0] [ProtectVms::PrepareConnectionAllocated] Peristing group op lock token for VM vm-50033
2025-12-01T12:42:09.178+01:00 panic vmware-dr[134098] [SRM@6876 sub=Default opID=1246b7c0]
-->
--> Panic: Assert Failed: _state != COMMITTED && _state != COMMITTED_REMOVE && _state != RELEASED (Persist called on a Reservation not in a persistable state: Committed) @ /build/mts/release/bora-24401761/srm/public/reservations/basicReservationImplDef.h:177
--> Backtrace:
--> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 9.0.2, build: build-24401761, tag: vmware-dr, cpu: x86_64, os: linux, buildType: release
--> backtrace[00] libvmacore.so[0x00252482]: Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
--> backtrace[01] libvmacore.so[0x0022B207]: Vmacore::System::SystemFactory::CreateBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
--> backtrace[02] libvmacore.so[0x0048CA7B]
--> backtrace[03] libvmacore.so[0x0048CB82]: Vmacore::PanicExit(char const*)
--> backtrace[04] libdr-license-manager.so[0x000E06BE]
--> backtrace[05] libdr-license-manager.so[0x000DA624]: Dr::Licensing::Reservation::Persist(BaseTransactionContext*)
--> backtrace[06] libdr-replication.so[0x005F537B]
--> backtrace[07] libdr-replication.so[0x005FF6F3]
--> backtrace[08] libdr-replication.so[0x003C3852]
--> backtrace[09] libpersistence-base.so[0x000255B1]
--> backtrace[10] libpersistence-base.so[0x00027E60]
--> backtrace[11] libvmacore.so[0x003429CE]
--> backtrace[12] libvmacore.so[0x003442D2]
--> backtrace[13] libvmacore.so[0x00497DE0]
--> backtrace[14] libpthread.so.0[0x00008EB0]
--> backtrace[15] libc.so.6[0x000FFADF]
--> backtrace[16] (no module)
--> [backtrace end]

Resolution

Follow below steps to remediate the issue - 

Remove VM by Removing from Inventory

1. Power Off the VM

   • Ensure the VM is not running

2. Remove VM from Inventory

   • Right-click VM → Remove from Inventory

   • Do not delete from disk

3. Rescan Arrays in SRM

   • Site Recovery → Array Based Replication

   • Run Rescan Arrays on both sites

4. Edit or Recreate Protection Group

   • Either:

     • Edit the existing PG and remove stale entries

     • OR delete and recreate the Protection Group

5. Re-register the VM 

   • Browse datastore → right-click .vmx → Register VM

Additional Information

Important Notes for Array-Based Replication

• SRM does not control replication — the storage array does.

• Removing a VM from a Protection Group:

  • Does not stop array replication

  • Does not delete datastore or VM files

• Always validate Consistency Group (CG) membership on the array side