Safely removing a job in EngageOne Vault (formerly E2 Vault)

There are specific steps to follow to remove a file from EngageOne® Vault, you cannot simply remove the files from the storage directories (includes vault_install_path\server\pagedata, vault_install_path\server\docdata, and vault_install path\server\storage) as this will cause the indexes to be corrupted and give end users error messages about missing files or invalid pointers.

To safely remove a file from EngageOne Vault (all versions)

1) Identify the name of the file you want to remove.  Typically you can use the name of the .drp or .jrn file.  For example:


2) In Notepad or a similiar text editor, create a new file with some content, can be spaces or any string value (for example hello world).  This file must have some size so cannot be completely empty, as errors will occur.

3) Name this file 20131123123453-somejobinthevault-e9df242a6790e34693f26a5ca2195a5b.remove (Alternatively, you can copy either the .drp or .jrn file to a location outside the Vault installation and change the extension to .remove)

4) While the Vault services are running, drop the file with the .remove extension (for example 20131123123453-somejobinthevault-e9df242a6790e34693f26a5ca2195a5b.remove) into the vault_install_path)/server/process directory

5) Monitor the process log (Vault versions 5.3m5 or lower) or the e2loaderd log (Vault versions 5.4 or higher) where the user will see information about the removal and un-indexing of the files.

6) Once the files are un-indexed, they are placed in the vault_install_path/server/removed directory. 
Environment Details
e2 Vault 5.3, 5.4, 5.5, 5.6, 6.0, 6.1 and 7.x  All platforms
UPDATED:  June 27, 2018