A Client trace shows the following :
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
EVMSP:
HDR: AutoReleaseSyncCoordinator::~AutoReleaseSyncCoordinator
HDR: EVMSPSyncCoordinator::Release
HDR: EVMSPSyncCoordinator::WaitForObject
HDR: ~EVMSPSyncCoordinator::WaitForObject
HDR: ~EVMSPSyncCoordinator::Release
HDR: ~AutoReleaseSyncCoordinator::~AutoReleaseSyncCoordinator
EVMSP:
The error MAPI_E_COLLISION is seen when the destination already contains a folder with the same name.
In a working scenario, when someone right-click deletes a folder in VV, the folder gets moved to the Deleted Items folder in VV. When that action is performed, the EV Add-In identifies the Deleted Items folder by checking the PR_IPM_WASTEBASKET_ENTRYID property. If this folder is not in the root of the data store, it moves it to the root and then performs the folder deletion.
This issue happens when the original 'deleted Items' folder is somehow moved to another folder hierarchy under the VV, and another 'Deleted Items' folder exists at the root of the data store. When a folder deletion is attempted, the EV Add-In identifies this 'Deleted Items' folder and checks if it is under the root of the VV data store. If not, it then tries to move the folder to the root. Since another folder named 'Deleted Items' already exists there, the move fails causing the folder deletion to fail.
Rename the 'Deleted Items' folder seen directly under the root of the VV data store.