Attempting to Mark items in Review has no effect and logs error Event ID 185 with code 0x80131904

book

Article ID: 100049274

calendar_today

Updated On:

Description

Error Message

 

Log Name: Veritas Enterprise Vault
Source: Accelerator Service Processor
Event ID: 185
Level: Error
Description: APP AS - Customer ID: X - An Error has occured when updating a marking item. System.Data.SqlClient.SqlException (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "FK_tblIntMarkHistory_tblPrincipal". The conflict occurred in database "", table "dbo.tblPrincipal", column 'PrincipalID'. ERROR_usp_DiscoveredItem_Upd_AddMark|X The statement has been terminated.

 

Cause

 

The CA/DA Clients communicate with the Accelerator server(s) and SQL server(s) to perform CA/DA functions using the ASP.NET protocol. As there can be a lot of data transferred during such communication, the Client will cache some data so as to provide faster updates for information that has not changed. When this cache is not updated properly or in a timely manner, it is considered stale and can cause unexpected behaviour in the Client.

 

Resolution

 

Manually refresh the Client cache as follows:

1. Open the CA or DA Client.
2. While pressing the Ctrl key on the keyboard, left-click on the Veritas logo in the lower right corner of the information bar at the bottom of the Client.
3. Monitor the middle of the information bar. The bar will display 'refreshing cache....', followed by 'Cache refreshed'.

Test Marking messages after the cache has been cleared. If the above method does not allow for Marking items, close the Client, restart the Enterprise Vault Accelerator Manager Service and IIS Service on the Accelerator server, then and reopen the Client and test Marking items.

 

Issue/Introduction

When attempting to Mark items in the Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA), some users may, on rare occasions, not see any Mark be applied to the item. Attempting to Mark additional items also results in those items not being Marked. No other Client behaviour seems to be affected. When this issue occurs, reviewing the EV Event Logs on the Accelerator server may show the Event ID as below.