Henfo,
I've seen the "0x80040e14" error be the result of a SQL error on the destination. Specifically, failure to insert a duplicate row in the destination vault store DB. Check your event logs on the source for any 13360 errors with "Cannot insert duplicate key row in object 'dbo.Saveset' with unique index 'IX_IdTransaction'."
If this is what is happening, then check the destination Vault Store to confirm the transaction is already there and what archive it is in:
a. Take the transaction and convert it to IdTransaction format:
Example from the reference above - F1515667-F34E-B6DA-6EDD-7E18C9D1FA41
b. Perform the following SELECT query on the destination vault store DB:
SELECT IdTransaction, IdDateTime, ArchivePointIdentity
FROM Saveset
WHERE IdTransaction = 'F1515667-F34E-B6DA-6EDD-7E18C9D1FA41'
c. If this returns a result, record the ArchivePointIdentity
d. Run the following SQL Query against the Vault Store DB to get the ArchiveID of the user:
SELECT ArchivePointID, ArchivePointIdentity
FROM ArchivePoint
WHERE ArchivePointIdentity = 'VALUE FROM b'
e. Record the ArchivePointID.
f. In the Vault Admin Console (VAC), Hold Shift+Ctrl and Right-click Archives.
- This will give a new option to Find Archive or Folder.
g. Paste the ArchivePointID here to find what archive the item is associated with.
It is very rare, close to impossible, to have a duplicate transaction randomly generated. Most commonly, this can be due to there being 2 archives on the destination due to a reattempt to move the archive from scratch and selecting new archive, even though an archive already exists there. If this item is located in one copy of the user's archive, yet you are now moving to a second instance of the users archive in the same site, the move will fail due to a duplicate record that does not exist in the archive you are moving to.
Is there more than one archive now in the destination site for this user?
I hope this helps.