The error is a SQL database issue.  The timeout is caused by SQL attempting to update the tables and cannot due to one of two issues: table index fragmentation or transaction log growth is taking too long to allocate the additional space required.

RESOLUTION:

A.  Manually shrink the Transaction log file
-- Step 1. Determine File Size before shrinking
DBCC SQLPERF(LOGSPACE)

-- Step 2. Switch recovery mode to Simple
ALTER DATABASE databasename -- replace databasename
SET RECOVERY SIMPLE
GO

-- Step 3. Shrink the truncated log file to 1 MB.
USE databasename  -- Replace the databasename
DBCC SHRINKFILE (logname_Log, 1)  -- Replace the logname_log
GO

-- Step 4. Reset the database recovery mode to Full.
ALTER DATABASE databasename  -- replace databasename
SET RECOVERY FULL;
GO

-- Step 5. Determine New File Size after shrinking
DBCC SQLPERF(LOGSPACE)



B. Set the Transaction log file for 'Enable Autogrowth' with unrestricted growth* and File Growth In Megabytes 500.

C. The number one action to perform in order to maintain a healthy Accelerator environment is to perform weekly Sql maintenance on the Accelerator customer database(s). The recommended actions are:

- Rebuild Indexes

- Update Statistics

- Shrink databases

To monitor the overall effectiveness of the weekly maintenance, run the following SQL command against each of the Accelerator customer databases:

Examine the results for two tables; tblIntDiscoveredItems and tblDiscoveredItemsToSearch.

- Logical Scan Fragmentation - under 1%

- Extent Scan Fragmentation - under 60%

- Avg. Page density (full) - over 90%

If the results exceed those limits, it is recommended to perform the action more frequently.

*** Note: Active searches and productions lock tables from maintenance. If there are active searches or productions during the maintenance routine the maintenance will skip those locked tables and complete. The tables will remain fragmented and no performance gain will be realized. It is recommended to stop the Enterprise Vault Accelerator Manager service prior to performing the maintenance run.