Enterprise Vault Event 3411 or Event 3432 - Troubleshooting Digest

Problem

Outlook on the Enterprise Vault (EV) server is unable to reach the Global Catalog (GC) in Exchange 2003, 2007 or Client Access Server (CAS) in Exchange Server 2010.

Example scenarios include:

• Exchange Archiving Task Failure
• Enable Mailbox Failure
• Running Provisioning Task
• EVPM Fails to Create a Privileged MAPI Session
• Recent Migration of Exchange
• OWA Retrievals

Error Message

Example event IDs include:

Event ID: 3411
Task Category: Agent Client Broker
Description: An error has been reported by ConfigureMsgService. It may be due to a problem contacting a Global Catalogue Server.
Exchange Server: 'EXCH-01'
Mailbox: SMTP:'VSA@mailbox.com'
Error: 0x80040115
V-437-3411

Event ID: 3432
Task Category: Archive Task
Description: One or more errors occurred during the creation of a profile to connect to an Exchange Server.
Targeted Exchange Server: 'EXCH-01'
Mailbox: SMTP:'VSA@mailbox.com'
ConfigureMsgService failed with the following errors:
A network error MAPI_E_NETWORK_ERROR has been reported for the following connection points:
S1-E2010-MBX01
V-437-3432

Log Name: Symantec Enterprise Vault 
Source: Enterprise Vault 
Date: 3/31/2016 12:18:31 PM 
Event ID: 3139 
Task Category: Agent Client Broker 
Level: Error 
Keywords: Classic 
User: N/A 
Computer: VAULT.Lab.com 
Description: 
An non-specific error has occurred whilst enabling archiving for the mailbox /o=Doe INC./ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=John Doe 
Error: <0x80040115> 
V-437-3139
 

Cause

In order to make a connection and open a specific mailbox, MAPI calls ConfigureMsgService. Errors reported by ConfigureMsgService can be broken down to the following areas:

1. Cannot resolve the system mailbox name - error 0x81002746

2. Connectivity errors to the NSPI end-point - error 0x80040115
    - MAPI_E_NETWORK_ERROR

In Event ID 3432, it notes an Exchange server or GC/DC.  Often times if a server is decommissioned and the GC is manually set in the Vault Admin console, it will cause this failure. 
(see Note 4 below to correct this)

3. Exceeded NSPI connections on Domain Controller - error 0x80040111 / 0x80040201
    - MAPI_E_LOGON_FAILED

4. Exceeded MAPI profiles (when using Outlook 2007)  - error 0x8007000e
    - MAPI_E_OUTOFMEMORY  See this Microsoft Article for more information.


 

Solution

Outlook, by default, will connect to the Global Catalog (GC) server or CAS automatically. If the GC or CAS is not readily available via the EV server one can be manually assigned.

There are two Outlook registry values used to resolve connectivity issues seen with ConfigureMsgService. These affect how the MAPI subsystem communicates with Active Directory and have no further impact on the EV environment.

For Exchange 2010 and 2013, use this registry key to force Outlook to use a pre-defined GC server.

Additional Information:

• This over-rides any setting in the MAPI profile.
• Using “DS Server” and multiple forests requires separate task accounts so individual “DS Server” values can be specified for the different forests.
• Use of the “DS Server” creates a single-point of failure – if the server is not available the tasks will fail and be unable to restart until the global catalog server becomes available again.
  
   

If running a version of Exchange Server that is earlier than Exchange Server 2010, use the following steps to force Outlook to identify and use the closest GC server.

When Closest GC is set to 1, Outlook automatically identifies and uses the closest global catalog server.
 

Note 1: Exchange Server 2010 introduces significant changes in the way Outlook interacts with GC servers in the organization. In Exchange Server 2010, the Microsoft Exchange Address Book Service on the CAS hosts the NSPI endpoint. The Exchange Server 2010 CAS provides address book and related services to Outlook clients instead of referring Outlook to GC server.
 

Note 2: Event 3411 was previously Event 3377 in Versions 7.5 SP6 and lower.
 

Note 3: A frequently used solution to resolve the single point of failure is to create a DNS round-robin for a selection of chosen GC servers. This allows a single connection point in configuration of Enterprise Vault while allowing the administrator to specify a set of GC servers they wish to use.

Note 4: To confirm if the GC is specified in the Vault Admin console, expand Site | Targets | Exchange | Right click > Properties on the Domain