Event ID 6511 about Storage File Watch failed to delete an item that could not be verified

Event ID 6511 about Storage File Watch failed to delete an item that could not be verified

Article: 100044381
Last Published: 2019-01-11
Ratings: 1 0
Product(s): Enterprise Vault

Problem

In rare circumstances the Event ID 6511 about "Storage File Watch failed to delete an item that could not be verified" could be logged at regular intervals during the day

Error Message

Following events could be logged together with the ID 6511:

Type :        Error
Event :       13405
Source :      Enterprise Vault 
Category :    Storage Archive
User :        N/A
Computer :    evserver1.domain.local
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

 

And Event ID 6511 as following: 

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

Cause

This issue has been observed with failed items archived on WORM devices (such as NetApp SnapLock) are not removed on failure (typically logging the error with Event ID 7109).

The same items are then attempted to be re-ingested from the StorageQueue causing the Event IDs 13405 and 6511.

Solution

This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.
 
Note:
Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.

References

JIRA : CFT-1537

Was this content helpful?