04-02-2024 03:12 AM - edited 04-02-2024 03:15 AM
Hi all,
After install March 2024 Exchange Server Security Updates I notice EVPM is not working:
EVPM.EXE" -e «exch_server» -m «ev_system_mbx» -f "c:\inifile.ini"
Setting Profile MailboxDN...
Creating privileged MAPI session ...
Error (0xc00408da) creating privileged MAPI session against Exchange Server SWEXLM91.ritta.local
I got this event.
Event: 7206
Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 2024-04-02 9:43:33
Event ID: 7206
Task Category: Policy Manager
Level: Error
Keywords: Classic
User: N/A
Description:
A locking error has occurred in CEVMAPILieModeLock : 0x102
Internal reference: STWL Thread Mutex CMailboxHelper::CreateProfileAndSessionAndOpenMailbox
Event:3230
Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 2024-04-02 9:43:33
Event ID: 3230
Task Category: Policy Manager
Level: Error
Keywords: Classic
User: N/A
Description:
Could not create a new MAPI session on Exchange server 'exch_server'.
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 <80320> <EVPM> Thread <11588>
Does anyone else have this problem?
04-02-2024 01:35 PM
I did not face this issue, but since this showing a mapie issue,please answer below questions:
-how long does it take for the error to repeat again? do you have to restart your the EV server?
-once the error is there, does everything work fine, or archive task fails / or archive tasks is not able to complete what it used to complete before?
04-02-2024 01:51 PM
Hi Kiyan,
It takes about a couple of minutes to abort the command.
I don't have any issues with the Enterprise Vault server (archiving, restoring, searching, etc.).
The only problem is that EVPM does not work. I attempted to zap an archive and exclude a folder from archiving, and got the error.
05-02-2024 02:08 AM
Hello,
The issue has ceased, and the reason is unclear.
It seems that the EVPM was executed with an incorrect user account.