Event ID 41619:
A transient error is preventing the execution of a SQL command. Enterprise Vault will try to run the command again.
Command: 'EVSqlDataAdapter: Select: EVSqlCommand: DB: server=SQLPRENV2;Initial Catalog=EVJA_OPCO;Integrated Security=true;Connection TimeOut=500;Connection LifeTime=200;Max Pool Size=300;Application Name=Compliance Accelerator - Command: usp_Items_FacetRangeCount_Select | Update: | Delete: Insert: '
Attempt: 1 of 40.
Last Error: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Execution Timeout Expired:
APP AT - Customer ID: 3 - Guaranteed Sampling: Error during guaranteed sampling - aborting. (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> 32Exception (0x80004005): The wait operation timed out
at [T](Func`1 action)
at (UsageStatsDS UsageStats, String IDsXML)
at _6_RecordUsageStats(Boolean isDeptLevelSampling)
at (WaitHandle[] waitHandles, Boolean checkRunNow)
ClientConnectionId:82d77b47-03fb-4ab8-9bea-0a75714f4aa8
Error Number:-2,State:0,Class:11
The root cause of the Event ID 41619 and Execution Timeout Expired errors can be attributed to several factors:
1. Connection Issue: The errors indicate a transient error preventing the execution of SQL commands, suggesting a connection issue between Enterprise Vault(EV) and the SQL server.
2. Resource Constraints: The SQL server may be experiencing resource constraints, such as high CPU or memory usage, leading to execution timeouts.
3. Search and Sampling Issues: The presence of pending, rejected, or failed searches in the system can contribute to performance issues and execution timeouts.
4. SQL Server Configuration: Inadequate SQL server configuration settings, such as the maximum degree of parallelism (MaxDOP) and cost threshold for parallelism, can impact query execution and result in timeouts.
To resolve the Event ID 41619 and Execution Timeout Expired errors in Enterprise Vault(EV) Compliance Accelerator(CA), follow these steps:
Verify Connection: Contact the SQL DBA to ensure there are no connectivity issues between EV and the SQL server. Reboot both the CA and SQL servers to refresh the connection.
Check Resource Usage: Monitor the resource usage on the SQL server, including CPU and memory utilization. Address any resource constraints that may be causing execution timeouts.
Review Search and Sampling Status: Analyze the CustomerDBReport to identify any pending, rejected, or failed searches. Review and either accept or reject pending searches, reject searches in paused status, and reject searches with no hits or failed status.
SQL Server Configuration: Consult with the SQL DBA to optimize the SQL server configuration. Adjust the MaxDOP setting to 4 and the cost threshold for parallelism to 50 to improve query execution performance.
Timeout Settings: Adjust the timeout settings in the CA Customer Properties from the EVBAAdmin site. Set the timeout values to 5000, 2000, and 500 for Connection Timeout, Connection Lifetime, and Max Pool Size, respectively.
Restart Background Tasks: Restart the Customer Background Tasks from the EVBAAdmin site .
Monitor and Test: Monitor the system for a few days to ensure the errors are resolved and the sampling process is functioning correctly. If the issue persists, continue monitoring and consider escalating the case to further investigate the root cause.