Error Message

Event Category: Storage Archive
Event ID: 13360
Description:
An error was detected while accessing the Vault Database 'Vault Store Name' (Internal reference: .\ADODataAccess.cpp (CADODataAccess::ExecuteSQLCommand) [lines {1356,1358,1373,1391}] built Feb 21 23:15:28 2007):
Description:
The SQL Server cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users or ask the system administrator to check the SQL Server lock and memory configuration.

SQL Command:
uspi_Saveset
Additional Microsoft supplied information:
Source: Microsoft OLE DB Provider for SQL Server
Number: 0x80040e14
SQL State: 42000
Native Error: 00001204
HRESULT 0x80040e14
V-437-13360

This can occur if there is an issue with SQL Server communicating to the Enterprise Vault server or the SQL Server is very busy. The request of the Storage Service to LOCK the Vault Store database fails and generates an Event ID 13360.

By restarting the Enterprise Vault Directory and Storage services, the existing SQL connections will be closed, some of which may have been orphaned, clearing out room for the acquisition of the LOCK.  While the LOCK is acquired the number of IndexCommited items will continue to rise.

Run the following SQL query against the Vault Store database listed in the Event Viewer error to determine the number of items awaiting to be indexed.

SELECT COUNT (*) FROM JournalArchive
WHERE IndexCommited = 0

Follow these steps to terminate any Enterprise Vault connection to the SQL server:

1. Stop the EV Storage Service
    
2. Open the SQL Management Studio and connect to the SQL Server where the EV databases are located.
    
3. Open Activity monitor by pressing CTRL+ALT+A
    
4. Go to Processes and sort by Database name.
    
5. Right-click on the row(s) that are related to the database in question and select kill process
    
6. Close the SQL Studio Management Console.
    
7. On the EV server, start the EV Storage Service.
    
8. Wait 10 minutes and confirm the index committed count begins to lower.
    
9. If the number does not decrease, additional investigation is needed to determine what query is locking the database.