Resolve "ERROR 74223: unable to delete file" in EngageOne Vault, formerly e2 Vault

Product Feature: Loader


User receives "ERROR 74223: unable to delete file" in the e2loader log.


This error occurs when the mirroring loader is attempting to update a file in server\distrib.

The file has been downloaded 
to a temporary folder (download.tmp) and the loader is trying to remove the existing version of the file before renaming the newly downloaded file into place.

In this case, another process has the file open (that's what Windows error code 32 means) and 
the deletion fails then the error is logged. 


UPDATED: November 7, 2017
This can occur in for a number of common reasons: 

(1) One of the servers is fetching the same file on behalf of an upstream client such as the Service Client which is being updated.
(2) A virus scanner or backup program has the file open as part of its operation.

If a subsequent "mirroring distrib" phase runs without error, the problem has resolved itself. Otherwise you'd need to use a tools(unlocker etc) to determine what the process that has the file open is. 

This type of error can, in theory, cause issues if it persists because it can leave the mirroring server with an inconsistent set of files in server\distrib which could lead to clients with an inconsistent set of files which might interfere with rendering, etc.