Event 8390 8391 13360 SQL database deadlock accessing the Vault Database

  • Article ID:100028743
  • Modified Date:
  • Product(s):


SQL Deadlock errors reported during run of the mailbox archiving task via event 8390 and 8391.

There are a few scenarios that will generate these events in the viewer. There can be too many active connections to the database. There could be a faulty ODBC connector from the EV server to the SQL database. SQL database collation configuration issues with-in the EV database could also produce a deadlocks scenario.

Error Message

Event ID: 8390
Task Category: Archive Task
Description: The EnterpriseVault.DirectoryConnection object reported an error. The SQL database server detected a deadlock while accessing the Vault Database '%2'

Event ID: 8391
Task Category: Directory Service
Description: The EnterpriseVault.DirectoryConnection object reported an error. The SQL database server detected a deadlock while accessing the Vault Database '%2'

Event: 13360
Category: Directory Service
Description: An error was detected while accessing the Vault Database 'Provider=SQLOLEDB;Server=server_name;Database=EnterpriseVaultDirectory;Trusted_Connection=Yes' (Internal reference: CC1):

Description: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

SQL Command: N/A
Additional Microsoft supplied information:
Source: Microsoft OLE DB Provider for SQL Server
Number: 0x80004005
SQL State: 42000
Native Error: 00018452
HRESULT 0xc0043433


Solution 1:
A task with too many open and active connections to the database may create a deadlock scenario.  This could occur as multiple processes access the same portion of the database.  To correct this occurrence:
1.      Lower the Number of concurrent connections to Exchange Server value from property of the Archive Task.
2.      The number of worker threads are based on the individual Mailbox
a.     Open the Vault Admin Console
b.     Navigate to the applicable Archiving Task | Properties | Settings
c.   Lower the Number of concurrent connections to Exchange Server
d.  The exact number is relative to the current setting

Solution 2:
A bad, corrupted or incorrectly set SQL ODBC connector on the EV server could create database deadlocks.  Verify / correct  SQL connectivity to the EnterpriseVaultDirectory database the ODBC connector on the on the EV server and following the steps below:
1.      Validate the EV Server OS version
a.      32bit C:\WINDOWS\system32\odbcad32.exe
b.     64bit C:\Windows\SysWOW64\odbcad32.exe
2.      Select the System DSN tab
3.      Highlight the EnterpriseVaultDirectory DSN connection and click the Configure
4.      Click next through the Wizard to the final screen and then chose the Test Data Source
5.      Verify the tests succeed or resolve any connectivity issues if the tests fail.
6.      Stop all Enterprise Vault services and run the command iisreset /noforce to restart the IIS services.

Solution 3:
If the collation in the SQL database is not unilateral across all of the EV database performance issues will surface.  To ensure that this is not the cause of the database deadlocks, please validate the collation in the SQL database.  There is an article dedicated to this topic 000081327.

Here is some additional information on the symptoms if collation issues are present in the EV database:
  • Messages can get stuck in the StorageArchive queue and can also see the deadlock in the EV databases.
    • These directly relate to archiving performance issues.
  • This problem can occur if the procedure to uniform the collations of the database was incorrectly executed or failed, leaving the Directory Database and/or the Vault Store databases, without any or some constraints.
    • This issue has been seen to be caused by missing constraints after a failed execution of the script to uniform the collation on the Enterprise Vault databases.
  • To verify this is the problem, please compare a backup of the EnterpriseVaultDirectory database as it was before changing the collations, with the resulting EnterpriseVaultDirectory database as it is after executing the script to change the collation.  A comparison may also need to be performed against each vault store database.

Related Articles

An Enterprise Vault (EV) upgrade fails due to SQL collation issues.

Was this content helpful?

Get Support