The Journal Archiving task and the JournalMailboxManager process get into an Exclusive Lock problem race condition

Problem

Every 15 minutes, a new process of the JournalMailboxManager will open the Journal Mailbox to check various statistics.  This can lead to an Exclusive Lock problem.

Error Message

The following Information Event will be logged every 15 minutes into the Enterprise Vault Event Log:

Type : Information
Event : 3430
Source : Enterprise Vault
Category : Task Controller Service
User : N/A
Computer : EVServerName.Domain.com
Description:
A request has been made to restart all the MAPI tasks.

There was a MAPI error from which Enterprise Vault cannot recover without restarting the tasks.
V-437-3430

In tandem with the above Information Event, the following events will occur from the Journal Task:

Type : Error
Event : 7206
Category : Journal Task
Description:
A locking error has occurred in CEVMAPILieModeLock : 0x102
Internal reference: STWL Write Mutex CMAPISession::CreateMapiSession
V-437-7206

Type : Error
Event : 3230
Category : Journal Task
Description:
Could not create a new MAPI session on Exchange server 'ExchangeServer1'.
The most likely cause is a connection issue that is causing excessive delays in the task. This can often be recovered by restarting the MAPI related tasks.

Internal References:
Unable to get exclusive access to the MAPI thread pool.
Mutex name: Lie mode lock
Reason: Last lock holder: Process <11424> Thread <10892>
V-437-3230

Type : Error
Event : 3305
Category : Journal Task
Description:
The Task 'Journal Task for ExchangeServer1' failed to log on to Exchange server 'ExchangeServer1' using mailbox 'SMTP:evaultmbxjrnl01@domain.com'.
Check that the mailbox has not been hidden, that the server is running and that the vault service account has sufficient permissions on the server.
V-437-3305

Type : Error
Event : 2258
Category : Journal Task
Description:
The Journal Task 'Journal Task for ExchangeServer1' could not be started due to startup errors.
V-437-2258

Type : Error
Event : 3460
Category : Journal Task
Description:
The Task 'Exchange Journaling Task for ExchangeServer2' failed to log on to Exchange server 'ExchangeServer2' using mailbox 'SMTP:evaultmbxjrnl02@domain.com'.
Check that the mailbox has not been hidden, that the server is running and that the vault service account has sufficient permissions on the server.

Enterprise Vault used the following settings for the Outlook Anywhere connection to Exchange 2013:
Proxy server: 'mail.domain.com'
Requires SSL: 'True'
Certificate principal: 'msstd:mail.domain.com'

If these settings are correct, check that the servers are responding.

Note that Enterprise Vault auto-discovers the proxy server and certificate principal unless you have configured them explicitly in the target domain's properties in the Administration Console, in which case you should check the settings you have made.
V-437-3460

Additional events from JournalMailboxManager that may also occur:

Type : Error
Event : 7206
Category : JournalMailboxManager
Description:
A locking error has occurred in CEVMAPILieModeLock : 0x102
Internal reference: STWL Write Mutex CMAPISession::CreateMapiSession
V-437-7206

Type : Error
Event : 3230
Category : JournalMailboxManager
Description:
Could not create a new MAPI session on Exchange server 'ExchangeServer1'.
The most likely cause is a connection issue that is causing excessive delays in the task. This can often be recovered by restarting the MAPI related tasks.
Internal References:
Unable to get exclusive access to the MAPI thread pool.
Mutex name: Lie mode lock
Reason: Last lock holder: Process <12116> Thread <27296>
V-437-3230

Cause

The JournalMailboxManager process is responsible for monitoring the Journal Mailboxes for Enterprise Vault, such as the number of items in the archive pending state.  This process uses a MAPI profile to connect to each Journal Mailbox every 15 minutes.  It can occur that the JournalMailboxManager process acquires an exclusive lock, or attempts to acquire one, which causes a Journal Archiving task thread to acquire an exclusive lock that becomes unresponsive.  If the attempt by the JournalMailboxManager to acquire an exclusive lock passes the 15 minute mark, the Task Controller Service will attempt to restart all Enterprise Vault MAPI tasks.  It has been seen that the JournalMailboxManager will not be restarted with the other Enterprise Vault MAPI tasks, which means that every 15 minutes the Task Controller Service will attempt to restart the Enterprise Vault MAPI tasks.  This pattern can be recognized in the Enterprise Vault event log as shown below:

Notice that errors are occurring every 15 minutes, and the Journal Mailbox will be seen to have stopped archiving.

Solution

This issue has been addressed in Enterprise Vault 11.0.0.  Release notes for each version of Enterprise Vault can be found here.

Notes:

1. These errors can also be seen in newer versions of Enterprise Vault.

2. For additional information, refer to Article 100013533