Deleting Research Folder items after viewing their History fails with foreign key constraint error

Deleting Research Folder items after viewing their History fails with foreign key constraint error

Article: 100032625
Last Published: 2018-04-12
Ratings: 0 0
Product(s): Enterprise Vault

Problem

Enterprise Vault (EV) Compliance Accelerator (CA) and Discovery Accelerator (DA) Reviewers have the ability to copy items to Research Folders for further review. Once Reviewed, these items may be deleted from the Research Folder as needed. The original items are still retained in the original Department (CA) or Case (DA).

If an item has had its History reviewed by clicking on the History tab in the item's preview, attempting to delete this item from the Research Folder's Review Set will fail with the error listed below; the error will reference tblXHeaders. In general, items that have not had their History reviewed may be deleted from the Research Folder's Review Set. If an item that has not had its History reviewed also cannot be deleted, the error will be similar but will reference tblIntSSIDJrnlReport.

Note: This behaviour is not seen when the Research Folder itself is deleted.

Error Message

Error referencing tblXHeaders:

The DELETE statement conflicted with the REFERENCE constraint "FK_tblXHeaders_tblIntDiscoveredItems". The conflict occurred in database "...", table "dbo.tblXHeaders", column 'DiscoveredItemID'.
The statement has been terminated.

User:        ...
Customer:    ...
Server:        ...
Domain:        Accelerator Client Domain
Stack:
    at Accelerator.Client.Review.ReviewPresenter.ItemUpdater_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
    at Accelerator.Client.Review.ItemUpdater.m_bulkOperationBackgroundWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
    at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
    at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

The DELETE statement conflicted with the REFERENCE constraint "FK_tblXHeaders_tblIntDiscoveredItems". The conflict occurred in database "...", table "dbo.tblXHeaders", column 'DiscoveredItemID'.
The statement has been terminated.:
Server stack trace:
    at KVS.Accelerator.Items.DiscoveryItems.UpdateDS(MultiDiscoveredItemDS DS)
    at KVS.Accelerator.RBO.RBO_Items.UpdateItems(Int32 proxyID, Int32 itemSetID, MultiDiscoveredItemDS mdiDS, ItemTagOperationCollection itemTagOps)
    at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at KVS.Accelerator.Interfaces.IItemSet.UpdateItems(Int32 proxyID, Int32 itemSetID, MultiDiscoveredItemDS mdiDS, ItemTagOperationCollection tagOps)
    at Accelerator.Client.Review.BulkOperationBackgroundWorker.ApplyBulkOperationToItems()
    at Accelerator.Client.Review.BulkOperationBackgroundWorker.BulkOperationBackgroundWorker_DoWork(Object sender, DoWorkEventArgs e)
    at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Cause

The Research Folder deletion processing did account for item entries in the tblXHeaders and tblIntSSIDJrnlReport tables; however, the item deletion processing did not account for entries in these tables.

Solution

This issue has been addressed in the following release:

Enterprise Vault 12.2.1
https://www.veritas.com/docs/100034312

Enterprise Vault 12.3
https://www.veritas.com/docs/100041266

References

Etrack : 3889992 JIRA : CFT-64

Was this content helpful?