EVSQ files stuck in the storage queue location, due to failure in re-ingestion by 'StorageArchive' process, with error "Constraint violation error" (Native Error: 00000547)
Article ID: 100047020
Updated On:
Description
Error Message
Event ID: 13405 A constraint violation error was detected while accessing the Vault Database 'EVVSVS01_2' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [d:\builds\16\ev\v-m-s\sources\source\common\adointerface\adodataaccess.cpp, lines {1325,1327,1346,1364}
, built Dec 18 21:06:18 2015]): |Description: |Enterprise Vault top level Stored Procedure : uspi_Saveset0, Error Procedure: uspci_WatchFile, Line 12, Error 547, Level 16, State 0, Message: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_TransactionId_WatchFile". The conflict occurred in database "EVVS", table "dbo.JournalArchive", column 'TransactionID'.| | |SQL Command: | uspi_Saveset0| | |Additional Microsoft supplied information:| |Source: Microsoft OLE DB Provider for SQL Server |Number: 0x80040e14 |SQL State: 42000 |Native Error: 00000547 |HRESULT|0x80040e14| |
Cause
Due to some unknown actions carried out on the database/items which are in re-ingestion state, entries in 'JournalArchive' table are missing for these items. In each re-ingestion cycle, the 'StorageArchive' process tries to insert entries in 'WatchFile' table and fails with error “Constraint violation error” as 'WatchFile table' has a foreign key constraint with 'JournalArchive' table and corresponding entries are missing.
Resolution
This issue has been addressed in the following releases:
Enterprise Vault 12.4.2, 12.5 and later versions.
Issue/Introduction
EVSQ files stuck in the storage queue location, due to failure in re-ingestion by 'StorageArchive' process, with error "Constraint violation error" (Native Error: 00000547).
Additional Information
JIRA: CFT-1451
