Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

error in archive

Created: 15 Aug 2012 | 15 comments

This is an event entry:  ( evadmin has same permissions on this account that it has on mine and I am on the same server; working properly)

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          8/11/2012 9:20:28 PM
Event ID:      3230
Task Category: Archive Task
Level:         Error
Keywords:      Classic
User:          N/A
Could not create a new MAPI session on Exchange server 'BHSMB3'.
Please ensure the privileged mailbox has not been hidden, the server is running and that the Vault account has sufficient permissions on the server.

Internal References:
Unable to get exclusive access to the MAPI thread pool.
Mutex name: EnterpriseVaultProfileMutex 1E44723FF760064419CD3159C914DF4E81011z00evserver1
Reason: WAIT_TIMEOUT (10 mins)

For more information, see Help and Support Center at
Event Xml:
<Event xmlns="">
    <Provider Name="Enterprise Vault " />
    <EventID Qualifiers="49156">3230</EventID>
    <TimeCreated SystemTime="2012-08-12T02:20:28.000000000Z" />
    <Channel>Symantec Enterprise Vault</Channel>
    <Security />
    <Data>EnterpriseVaultProfileMutex 1E44723FF760064419CD3159C914DF4E81011z00evserver1</Data>
    <Data>WAIT_TIMEOUT (10 mins)</Data>

Comments 15 CommentsJump to latest comment

JesusWept3's picture

what version of enterprise vault are you using?
what version of outlook and service pack do you have installed on the ev server?
what version of exchange are you targeting?
Can you connect to the EV System mailbox its complaining about on the EV Server logged on as the EVAdmin account?
Is that system mailbox definitely not hidden?
Is that System mailbox definitely on the exchange server that is being targeted? (sometimes people move the mailboxes to another exchange server and then the call fails)
Are you targeting multiple domains?
Do you use either Closest GC or DS Server registry keys?

pmo051's picture

I should have been more forthcoming... Doesn't everyone have my configuration?? haha

EV version - 9.02

Outlook 2007 sp3

Exchange 2010 (sp2 ru2)

I can open the mailbox using the EV Admin account

not hidden




JesusWept3's picture

OK so , have you always been getting these errors or have they only just started?
when was the last time you rebooted the EV Server?
Are there any errors on any of your Exchange 2010 CAS Servers regarding the EVAdmin account?

Rob.Wilcox's picture

Did you implement the throttling policy for EV?

I mean .. it's waiting *10 minutes* for a mutex.

That's twice as long as infinity.. nearly.

pmo051's picture

nothing showing in event log on CAS array.

I reboot the EV box about every week -- seems to help keep it 'regular'.

pmo051's picture

[PS] C:\Windows\system32>Get-ThrottlingPolicyAssociation -Identity evadmin

RunspaceId         : 9b4cdb3a-bc21-4608-a06c-4051b6d880a3
ObjectId           : Accounts/Exchange Messaging/Enterprise Vault Admin
ThrottlingPolicyId : EnterpriseVault_D0F41A15-9E91-D111-84E6-0000F877D428
Name               : Enterprise Vault Admin
IsValid            : True
ExchangeVersion    : 0.10 (
DistinguishedName  : CN=Enterprise Vault Admin,OU=Exchange Messaging,OU=Admin Accounts,DC=bhsala,DC=com
Identity           : Accounts/Exchange Messaging/Enterprise Vault Admin
Guid               : e9999cfe-8b51-4a56-ba0a-7d35c337f455
ObjectCategory     :
ObjectClass        : {top, person, organizationalPerson, user}
WhenChanged        : 8/12/2012 12:00:31 PM
WhenCreated        : 6/14/2010 9:58:20 AM
WhenChangedUTC     : 8/12/2012 5:00:31 PM
WhenCreatedUTC     : 6/14/2010 2:58:20 PM
OrganizationId     :
OriginatingServer  :

Rob.Wilcox's picture

What about the output from :


.. I'm just wondering if the Throttling Policy is interfering from time to time.

Look to see if the null's are in the right properties:

Set-ThrottlingPolicy $EVPolicyName -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null

LCT's picture

From your Get-ThrottlingPolicyAssociation -Identity evadmin result it shows:

ExchangeVersion : 0.10 (

This means that the result is telling you that you are running exchange 2010 BASE version, it should show something like 14.01.0218 for SP1 and 14.02.0247 for SP2. This could be the cause of your problem?

You said you are using exchange 2010 SP2 RU2? Are you running mismatch exchange 2010 SP versions i.e. different CAS and MBX server SP versions etc?

Here is the post that someone was using 9.0.1 (not sure what the exchange version) and Alex had helped them through a lot of the MAPI troubleshoting steps.

Long shot but I would take Outlook 2007 SP3 off and install Outlook 2007 SP2 plus a couple of required hotfixes (check the compaitibility chart for more details). I have had a few customers upgrading Outlook 2007 from SP2 to SP3 and experienced MAPI issues, although Outlook 2007 SP3 supposedly fixed a few issues. :-)

Also check your EV exchange mailbox archiving policy to clear out MAPI connection after 1 day (i think by defaults it is set to 3 days). This may also help.

Rob.Wilcox's picture

Regarding the version information my server is 110% definitely running 2010 SP 1 :

[PS] C:\Windows\system32>get-exchangeserver | fl name, edition, admindisplayversion
Name                : DC
Edition             : StandardEvaluation
AdminDisplayVersion : Version 14.1 (Build 218.15)

But the Get-ThrottlingPolicyAssociation outputs the same as the original poster...

[PS] C:\Windows\system32>get-throttlingpolicyassociation -identity vaultadmin
RunspaceId         : fb2431c1-72a0-49e5-96f7-13b0e0e0ed19
ObjectId           : ev.local/Users/vaultadmin
ThrottlingPolicyId : EnterpriseVault_D0F41A15-9E91-D111-84E6-0000F877D428
Name               : vaultadmin
IsValid            : True
ExchangeVersion    : 0.10 (
DistinguishedName  : CN=vaultadmin,CN=Users,DC=ev,DC=local
Identity           : ev.local/Users/vaultadmin
Guid               : e26cf6ca-9374-4aef-9e23-61bf9bbee59d
ObjectCategory     : ev.local/Configuration/Schema/Person
ObjectClass        : {top, person, organizationalPerson, user}
WhenChanged        : 10/08/2012 07:47:20
WhenCreated        : 18/06/2012 12:00:54
WhenChangedUTC     : 10/08/2012 06:47:20
WhenCreatedUTC     : 18/06/2012 11:00:54
OrganizationId     :
OriginatingServer  : dc.ev.local
So.. I don't think that is related.
LCT's picture


So you have determined that it is running Exchange 2010 SP1 (which is fair enough), I suspected it is running Exchange 2010 BASE (from the information above), and pmo051 "confirmed" it is running Exchange 2010 SP2 RU2? :-)


Could you run

[PS] C:\Windows\system32>get-exchangeserver | fl name, edition, admindisplayversion
and see what you get?
I know this is more exchange side of things and I agree with Rob that it's probably not related to your issue but I'd be interested to see if you get something like
AdminDisplayVersion : Version 14.2 (Build xxx.xx) for exchange 2010 SP2

Reason I ask is that I have seen EV side of things especially in the EV OWA 2010 extensions showing the wrong version of exchange. I'll get my lab up and show this to you at some point.

pmo051's picture

[PS] C:\Windows\system32>get-exchangeserver | fl name, edition, admindisplayversion

Name                : BHSFE1
Edition             : Enterprise
AdminDisplayVersion : Version 14.2 (Build 247.5)

Name                : BHSFE2
Edition             : Enterprise
AdminDisplayVersion : Version 14.2 (Build 247.5)

Name                : BHSMB3
Edition             : Enterprise
AdminDisplayVersion : Version 14.2 (Build 247.5)

Name                : BHSMB4
Edition             : Enterprise
AdminDisplayVersion : Version 14.2 (Build 247.5)

LCT's picture


That looks more like Exchange 2010 SP2. Although when you and Rob run

[PS] C:\Windows\system32>Get-ThrottlingPolicyAssociation -Identity evadmin

The exchange version it shows this:

ExchangeVersion    : 0.10 (
perhaps it's an exchange bug. Sorry to divert your issue a little.
Were you able to go through the MAPI troubleshooting from the link above? And as Alex already asked do you use either Closest GC or DS Server registry keys on the EV server?
Do you have BES and Mobile Device apllication such as Good Technology?
What is your CAS server(s) environment? do you use Windows NLB or cluster of any sort? reason I ask is because someone has posted the same problem as you have.
pmo051's picture

A bit bogged down in the day-to-day;

We do have a BES (5.0) -- I have not set any reg keys for Closest CG.

I am using NLB for my frontend / CAS Array.

I will try to get through the TS link during lunch.. I don't get this from any other mailbox servers. Always from MB3. -- every 10 minutes, 4 tries.

LCT's picture

Here's my results as promised:

[PS] C:\Windows\system32>Get-ThrottlingPolicyAssociation -Identity svc_ev

RunspaceId         : e186af71-c063-4d8f-8cc3-d6333d5ff8c7
ObjectId           : Admin Users/svc_ev
ThrottlingPolicyId : EnterpriseVault_D0F41A15-9E91-D111-84E6-0000F877D428
Name               : svc_ev
IsValid            : True
ExchangeVersion    : 0.10 (
DistinguishedName  : CN=svc_ev,OU=EV Admin Users,DC=domain,DC=com
Identity           : Admin Users/svc_ev
Guid               : b532bc40-176b-4c27-bd55-2429bc097f63
ObjectCategory     :
ObjectClass        : {top, person, organizationalPerson, user}
WhenChanged        : 16/08/2012 20:06:19
WhenCreated        : 19/07/2012 22:18:09
WhenChangedUTC     : 16/08/2012 19:06:19
WhenCreatedUTC     : 19/07/2012 21:18:09
OrganizationId     :
OriginatingServer  :

[PS] C:\Windows\system32>get-exchangeserver | fl name, edition, admindisplayversion

Name                : CASServer
Edition             : Enterprise
AdminDisplayVersion : Version 14.2 (Build 247.5)

Name                : MBXServer1
Edition             : Enterprise
AdminDisplayVersion : Version 14.2 (Build 247.5)

Name                : MBXServer2
Edition             : Enterprise
AdminDisplayVersion : Version 14.2 (Build 247.5)

This part I get the same as you guys so i suspect it's an exchange bug.

However, in my EV OWA Logs I get:

21/07/2012 21:43:23 [5760,1] EV Extensions DLL version:

21/07/2012 21:43:23 [5760,1] EwsRequest:
<Trace Tag="EwsRequest" Tid="1" Time="2012-07-21 20:43:23Z" Version="14.01.0218.002">
  <?xml version="1.0" encoding="utf-8"?>
  <soap:Envelope xmlns:xsi="" xmlns:m="" xmlns:t="" xmlns:soap="">
      <t:RequestServerVersion Version="Exchange2010_SP1" />

My point here is that the EV OWA extentions thinks that exchange is Exchange 2010 SP1 and the results above showed otherwise. I suspect this is an EV bug, unless EV codes is usingthe same query to look up for the exchange version in exchange the the whole is screwed LOL....

Anyway, back to your original issue :-)