Enterprise Vault archiving tasks experience connection issues with Exchange 2013 targets

Article:TECH198553  |  Created: 2012-10-18  |  Updated: 2014-09-25  |  Article URL http://www.symantec.com/docs/TECH198553
Article Type
Technical Solution


Issue



** Updated: April 26, 2013 **

 

The problem as described is fixed in Exchange 2013 Cumulative Update 1. The workarounds as described below are no longer required after installing or upgrading to Exchange 2013 CU1. Any customer now running CU1 (or later) that has implemented Option 1 should remove the registry value from their Exchange mailbox servers.

 

Enterprise Vault Exchange mailbox, journal, and public folder archiving tasks experience connection issues. This generates error messages in the event logs, and the tasks sleep unexpectedly. This issue is more likely to occur on Enterprise Vault servers that host multiple Exchange archiving tasks.

 

This issue arises from changes to the handling of session limits on the mailbox server in Exchange 2013. User accounts with administrative privileges can override these session limits but Exchange 2013 is not counting administrative sessions correctly.

 

Microsoft is aware of this issue. Until it is fixed, use one of the workarounds in this article.


Error



From any of the Exchange archiving tasks, on the Enterprise Vault server:

Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Event ID: 3231
Task Category: Archive Task
Level: Error
Keywords: Classic
User: N/A
Computer: e15vault.15dom.local
Description:
Could not get a MAPI session from the session pool.

Error: <0x8004011d>
Source: Exchange Mailbox Archiving Task for E15MBX
Additional Information: Whilst processing user /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) /cn=Recipients/cn=83d0a43be73847b3bbaf4e7a96530b24-d1-1

V-437-3231

Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Event ID: 3419
Task Category: Archive Task
Level: Warning
Keywords: Classic
User: N/A
Computer: e15vault.15dom.local
Description:
Could not access Exchange Server. The dispenser will queue the current item and sleep for 60 seconds. Task: Exchange Mailbox Archiving Task for E15MBX

 V-437-3419

From of the Exchange journal archiving task, on the Enterprise Vault server:

Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Event ID: 3237
Task Category: Journal Task
Level: Error
Keywords: Classic
User: N/A
Computer: e15vault.15dom.local
Description:
An error occurred opening the Journaling mailbox /O=FIRST ORGANIZATION/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=D7B82AB3C94A4CA0BACDE258C8D31E29-JOURN

Check that the message store is available and the mailbox is accessible

 V-437-3237

Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Event ID: 2910
Task Category: Journal Task
Level: Error
Keywords: Classic
User: N/A
Computer: e15vault.15dom.local
Description:
An error in CArchivingAgent::SetupAndCallQueueMsg() occurred whilst creating the objects that are needed.

V-437-2910

 

On the Exchange mailbox server:

Log Name: Application
Source: MSExchangeIS
Event ID: 9646
Task Category: MAPI
Level: Error
Keywords: Classic
User: N/A
Computer: e15mbx.15dom.local
Description:
Mapi session /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=57cbb5977c114cd099fc16d2d3ea5767-sysmb with client type MoMT exceeded the maximum of 32 objects of type Session.


Cause



Exchange 2013 has changed behavior for overriding the maximum number of sessions allowed on a mailbox server. Accounts connecting with administrative permissions can override the session limit. However, there is currently an issue in Exchange 2013 that is not counting administrative sessions correctly. This issue does not affect earlier versions of Exchange.


Solution



Microsoft recognize this as an issue. Until it is resolved, use one of the following workarounds.


Option 1


Use the Maximum Allowed Sessions Per User registry key to increase the number of allowed MAPI sessions per user, including the Vault Service account.


Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. You should back up the registry and your data before you make registry changes.

 

  1. On each Exchange 2013 mailbox server, create a new registry DWORD value called Maximum Allowed Sessions Per User under the following registry key:

    \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
     
  2. Set Maximum Allowed Sessions Per User to 0x00001388 to allow up to 5,000 sessions per user.


Note: There is no specific upper-limit to this setting beyond the limits that are imposed by it being a DWORD.


For more information, see the following page on the Microsoft website (this page applies to both Exchange 2013 and Exchange 2010):

 

http://technet.microsoft.com/en-us/library/ff477612.aspx

 

In some circumstances it may not be desirable to set the limit for allowed sessions per user to 5,000. Use the following formula to determine the maximum allowed sessions per user. This is only a guide and it may be necessary to increase the limit further. The formula does not make allowance for Discovery Accelerator, Compliance Accelerator, or Custodian Manager. The final value created is decimal and you must convert this to hexadecimal before you set the registry DWORD value.

 

A = Number of mailbox archiving tasks × Number of connection threads (per task) × 4
B = Number of journal archiving tasks × Number of connection threads (per task) × 4
C = Number of public folder archiving tasks × Number of connection threads (per task) × 4
D = Number of Enterprise Vault servers with task controller service running × 20
E = Number of Enterprise Vault servers with storage service running × 32
F = Number of Enterprise Vault servers with shopping service running × 32
G = Number of Enterprise Vault servers carrying out PST migrations × 20

 

Total = 2 × (A + B + C + D + E + F + G)

 

Option 2


Configure each Exchange archiving task to run under a different user. This means that the 32 MAPI session store limit per user should not be reached because each task has its own 32 session limit, rather than sharing a single 32 session limit.

 

  1. Stop all Exchange archiving tasks.
     
  2. For each Exchange archiving, mailbox, journal, and public folder task, create a new user with an Exchange mailbox.
     
  3. Grant each user the required Enterprise Vault and Exchange Server permissions using the Enterprise Vault documentation.
     
  4. Go to the each Exchange archiving task's Log on tab.
     
  5. Click Use this account.
     
  6. Enter the newly user account to be used with the task.
     
  7. Enter the password for the user account.
     
  8. Click OK to commit the task properties changes.
     
  9. Restart the Exchange archiving tasks.

 


Supplemental Materials

SourceEvent ID
Value3231
Description

Could not get a MAPI session from the session pool.


SourceEvent ID
Value3419
Description

Could not access Exchange Server. The dispenser will queue the current item and sleep for 60 seconds. Task: Exchange Mailbox Archiving Task for


SourceEvent ID
Value3237
Description

An error occurred opening the Journaling mailbox


SourceEvent ID
Value2910
Description

An error in CArchivingAgent::SetupAndCallQueueMsg() occurred whilst creating the objects that are needed.



Article URL http://www.symantec.com/docs/TECH198553


Terms of use for this information are found in Legal Notices