When Accepting a Search in Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA), the Search remains in the Accepted status and does not progress to the Accepting or In Review statuses. This behaviour is independent of manually Accepting a Search or using the 'Automatically Accept' Search option. A review of the EV Event Log on the Accelerator Server shows the Events below. Restarting the Customer's Background Tasks, the Enterprise Vault Accelerator Manager Service or the Accelerator server has no effect on the issue. No other CA/DA functions appear to be affected. Items already in Review can be Previewed and Marked, and Exports can be run. New Searches can be submitted and will complete, but will not be able to be Accepted.
Event ID: 308
Description: APP AT - Customer ID: X - An Error has occured accepting a Search. System.Data.SqlClient.SqlException (0x80131904): Arithmetic overflow error converting expression to data type int. Cannot insert the value NULL into column 'DiscoveredItemId', table '<Customer database>.dbo.tblHashToDiscoveredItem'; column does not allow nulls. INSERT fails. Arithmetic overflow error converting expression to data type int. ERROR_usp_DiscoveredItem_Add_Insert|<CaseID>|<SearchID> Arithmetic overflow error converting expression to data type int. Cannot insert the value NULL into column 'DiscoveredItemId', table '<Customer database>.dbo.tblHashToDiscoveredItem'; column does not allow nulls.
Event ID: 287
Description: APP AT - Customer ID: X - Error accepting a Search: Accepted Search Thread - worker thread (X) Search ID: X Number of tries: 0
When a Search is Accepted, data associated to the Search results is processed by the SQL server. This is performed in the Accelerator Customer database via the use of stored procedures which process the data using variables to temporarily store the data being processed. As required by SQL, these variables are defined with specified data types, where each data type has it's own predefined and non-editable limits. The issue is caused by the Search Acceptance processing attempting to provide data to a variable that exceeds that variable's data type specification's limits.
Veritas has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.
This issue is currently under investigation by Veritas. Pending the outcome of the investigation, this issue may be resolved by way of a cumulative hotfix, release update or service pack in the current or future versions 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. For information on how to contact Veritas Sales, please see https://www.veritas.com .
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):