Lie Mode Lock causing the Archiving Task to restart every 10-15 minutes

Problem

Event Id's 7206, 3230, 3430, 3296 are logged when Enterprise Vault is unable to get an exclusive access to the MAPI thread pool.

Error Message

Enterprise Vault logs the following events:

Log Name:Enterprise Vault
Source:Enterprise Vault
Event ID:7206
Task Category:Archive Task
Level:Error
Description:A locking error has occurred in CEVMAPILieModeLock : 0x102 
Internal reference:STWL Write Mutex CMAPISession::CreateMapiSession
V-437-7206

Log Name:Enterprise Vault
Source:Enterprise Vault
Event ID:3230
Task Category:Archive Task
Level:Error
Description:Could not create a new MAPI session on Exchange server 'HS099XCH6'.
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.
V-437-3230

Internal References:
Unable to get exclusive access to the MAPI thread pool.
Mutex name:Lie mode lock
Reason:Last lock holder: Process <15908> <ArchiveTask> Thread <1304>

Log Name:Enterprise Vault
Source:Enterprise Vault
Event ID:3430
Task Category:Task Controller Service
Level:Information
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

Log Name:Enterprise Vault
Source:Enterprise Vault
Event ID:3296
Task Category:Archive Task
Level:Information
Description:The Archiving Task 'Exchange Mailbox Archiving Task for HS099XCH6' against HS099XCH6 has stopped. This is a normal shut down, no action is required. 
V-437-3296

Backtrace Logs captured the following:

19466 10:03:15.110  [15908] (ArchiveTask) <6860> EV:L {GetDomainNamingContexts:#105} Binding using string [GC://gc.abc.hu/RootDSE]
20142 10:18:15.193  [15908] (ArchiveTask) <2140> EV:L {CReadWriteLock::SetWriteLock:#369} [CEVMAPILieModeLock] WaitForSingleObject on write mutex [0x1B0] returned [0x102]
20143 10:18:15.193  [15908] (ArchiveTask) <2140> EV:H {CReadWriteLock::SetWriteLock:#373} WaitForSingleObject failed with result [0x102]
20144 10:18:15.193  [15908] (ArchiveTask) <14600> EV:L {CReadWriteLock::SetWriteLock:#369} [CEVMAPILieModeLock] WaitForSingleObject on write mutex [0x1B0] returned [0x102]
20145 10:18:15.193  [15908] (ArchiveTask) <14600> EV:H {CReadWriteLock::SetWriteLock:#373} WaitForSingleObject failed with result [0x102]
20146 10:18:15.193  [15908] (ArchiveTask) <2140> EV~E Event ID: 7206 A locking error has occurred in CEVMAPILieModeLock : 0x102  |Internal reference: STWL Write Mutex CMAPISession::CreateMapiSession |
20150 10:18:15.333  [15908] (ArchiveTask) <2140> EV~E Event ID: 3230 Could not create a new MAPI session on Exchange server 'HS099XCH6'. |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 <15908> <ArchiveTask> Thread <1304> |
20152 10:18:15.505  [15908] (ArchiveTask) <2140> EV:H {CEVMAPILieModeLock::SignalAllMAPITasksToRestart:#157} Setting the 'restart MAPI tasks' event to signaled...

Cause

1. Closest GC (Global Catalog) registry key implemented:

2. ​GC has beem hardcoded in Vault Admin Console.

Solution

Remove:

1. Improperly configured Closest GC Key value:

   Key	Location	Settings
   Closest GC	HKEY_CURRENT_USER \Software   \Microsoft      \Exchange       \Exchange Provider	Value name: Closest GC   Data type: REG_DWORD   Radix: Hexadecimal  Value data: 0x00000001

2. Hardcoded GC from Vault Admin Console.

1. DS Server registry key value of the Fully Qualified Domain Name FQDN of CAS Array

   Key	Location	Settings
   DS Server	HKEY_CURRENT_USER \Software   \Microsoft      \Exchange       \Exchange Provider	Value name: DS Server   Data type: REG_SZ (string)   Value data: FQDN of the CAS server

Also refer to Article 100012379.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to the Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.