Event 3419 MAPI error detected for an Exchange 2010 or later target (possible DAG failover) - 0x80040115 OR Task failing with Event 3305 and 2258
|Article:TECH169970|||||Created: 2011-09-20|||||Updated: 2014-02-20|||||Article URL http://www.symantec.com/docs/TECH169970|
The Enterprise Vault Event log contains Events 3419 and 2217.
The HRESULT 0x800400115 (MAPI_E_NETWORK_ERROR) is the cause of the event. These events start occurring 5-7 minutes after the tasks have started and are typically repetitive and occur approximately every 5 to 7 minutes once the initial issue is encountered. This can lower over all performance when archiving an Exchange 2010 environment.
The task failing with generic Event 3305 and 2258
The HRESULT 0x8004011d (MAPI_E_FAILONEPROVIDER) is the cause of the event.
The following is an example of the error message:
Event ID 3419:
There was a problem accessing an Exchange 2010 or later server. The dispenser will re-queue the current item and sleep for 1 minute(s).
Event ID: 2217:
Message dispenser will resume processing
When performing a Dtrace of JournalTask or Archive Task, this will report HRESULT: 0x80040115
EV:M CExchangeShortcutAccessor::SetSession - Call to OpenEntry Failed [0x80040115] - Retrying
For the Archive Task:
EV:M MAPI error detected for an Exchange 2010 or later target (possible DAG failover) - 0x80040115
Netmon Log Shows
Hardware and software load balancing appliances actively harden TCP traffic overheads in an effort to stop all potential high bandwidth traffic from causing network delays. All communication that occurs between the Enterprise Vault Server is TCP traffic. These connections between Microsoft Exchange and the Enterprise Vault Server are usually open for extended periods of time. When a load balancer is implemented with a Microsoft Exchange Server, all TCP traffic is given a timeout value. This timeout value actively ceases all extended TCP sessions between the two communication points.
Bypass the hardware load balancer with a hosts file entry so that the Enterprise Vault Server may communicate directly with a single Client Access Server (CAS).
1. Browse to c:\Windows\System32\drivers\etc and edit the hosts file.
2. Create an entry with the IP address of one of the CAS nodes and the network name of the hardware load balancer. The name of the hardware load balancer will match the Exchange 2010 CAS Array name.
10.10.10.34 (IP address of the CAS Node) CASArray.domain.com (Fully Qualified Domain Name of the CAS Array)
3. Save the file.
4. Open a Command Prompt and run ipconfig /flushdns
5. Restart the Enterprise Vault Task Controller Service.
Increase the default TCP Session Timeout on the applicable Load Balancing Appliance.
Note: For further assistance to increase this timeout value, please contact the appliance vender.
Article URL http://www.symantec.com/docs/TECH169970