Problem
In a mixed mode environment with both Exchange 2010 & 2013 or 2016 Client Access/Mailbox servers the Archiving Task can fail to connect though a connection via Outlook on the Enterprise Vault (EV) server to the EV System Mailboxes is successful.
Error Message
A Dtrace of the ArchiveTask process shows the following error.684 09:33:04.696 [10276] (ArchiveTask) <14576> EV:L {HrMAPIOpenMsgStoreKvs:#50} Opened msg store [0x8004011d]
685 09:33:04.696 [10276] (ArchiveTask) <14576> EV:H {CMailboxHelper::OpenMailbox:#302} Could not open message store: [0x8004011d]
Cause
The issue can have multiple causes therefore the solution contains multiple points to check.Solution
Review and confirm the following.- Exchange Throttling Policies applied correctly
- The Vault Service Account associated mailbox has been moved to the Exchange 2013 servers.
- Check correct Outlook version and service are applied on the EV Server. .
- Check at least 10.0.4 CHF 3 is installed so mixed mode environments are supported.-
- Check the AutoDiscoverServiceURI setting for Exchange 2010 Client Access Server to see if this has been pointed to the Exchange 2013 or 2016 Client Access Server. The following command will show this.
Get-ClientAccessServer | fl Name, AutoDiscoverServiceInternalUri
If configured to point to Exchange 2013 or 2016 Client Access Server for 2010 connections, this will force Outlook to use RPC over HTTP (Outlook Anywhere) to connect to Exchange 2010, which is not supported with EV and Exchange 2010. For Exchange 2010 servers, the Client Access Server must be an Exchange 2010 Client Access Server, as this will allow EV to connect to the Exchange 2010 mailbox using RPC over TCP (MAPI).
EV will detect that the mailbox resides on Exchange 2010 and then utilize an RPC connection only, which will fail via Exchange 2010. To check the connection type open the connection status on the EV Server when connected to the System Mailbox located on Exchange 2010. Hold down CRTL/SHIFT and right-click Outlook icon in the system tray and open Connection Status.
Correcting this is outside of the scope of EV as this is an Exchange configuration change. Further information can be found using the following link.
Set-ClientAccessServer
- In addition altering the RPClientAccessServer attribute can alter the behavior to be similar to altering the AutoDiscoverServiceInternalUri attribute. Again this is outside of the scope of EV and you can reference the below.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.