The following events could be logged together with the ID 6511:
Type : Error
Event : 13405
Source : Enterprise Vault
Category : Storage Archive
Description:
A constraint violation error was detected while accessing the Vault Database 'EVVSDatabase' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [d:\builds\16\ev\v-m-s\sources\source\common\adointerface\adodataaccess.cpp, lines {1326,1328,1347,1365}, built Aug 15 09:12:16 2017]):
Description:
Enterprise Vault top level Stored Procedure : usp_FinishSavesetInsert0, Error Procedure: uspci_WatchFile, Line 12, Error 2627, Level 14, State 1, Message: Violation of UNIQUE KEY constraint 'UN_WatchFile_SavesetIdentity'. Cannot insert duplicate key in object 'dbo.WatchFile'. The duplicate key value is (xxxxxx).
SQL Command:
usp_FinishSavesetInsert0
Additional Microsoft supplied information:
Source: Microsoft OLE DB Provider for SQL Server
Number: 0x80040e14
SQL State: 42000
Native Error: 00002627
HRESULT 0x80040e14
V-437-13405
Event ID 6511 is as the following example from a test lab environment:
Type : Error
Event : 6511
Source : Enterprise Vault
Category : Storage File Watch
Description:
Storage File Watch failed to delete an item that could not be verified
VaultStore Ptn1
14F630B7BA203074E98CFE2EC8E0D414E1110000vault
2018\07-18\6\088\608812161BD29333804754EB130C7BE1.DVS
608812161BD29333804754EB130C7BE1
V-437-6511
This issue has been observed with failed items archived on WORM devices (such as NetApp SnapLock) that are not removed on failure (typically logging the error along with Event ID 7109).
The same items are then attempted to be re-ingested from the StorageQueue, causing the Event IDs 13405 and 6511.
This issue has been addressed in the following release(s):
Enterprise Vault 12.4.1
In rare circumstances, the Event ID 6511 with the error Storage File Watch failed to delete an item that could not be verified could be logged at regular intervals during the day.
JIRA: CFT-1537