Enterprise Vault Event 3411 or Event 3432 - Troubleshooting
|Article:TECH139751|||||Created: 2010-09-14|||||Updated: 2013-11-22|||||Article URL http://www.symantec.com/docs/TECH139751|
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
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'
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'
ConfigureMsgService failed with the following errors:
A network error MAPI_E_NETWORK_ERROR has been reported for the following connection points: S1-E2010-MBX01
In order to make a connection and open a specified 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
3. Exceeded NSPI connections on Domain Controller - error 0x80040111 / 0x80040201
4. Exceeded MAPI profiles (when using Outlook 2007) - error 0x8007000e
- MAPI_E_OUTOFMEMORY See TECH129173 for more information.
Outlook, by default, will connect to the GC 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 use this registry key to force Outlook to use a pre-defined GC server.
- 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.
Value name: DS Server
Data type: REG_SZ (string)
Value data: FQDN of the CAS server
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.
Value name: Closest GC
Data type: REG_DWORD
Radix: Hexadecimal Value data: 0x00000001
When Closest GC is set to 1, Outlook automatically identifies and uses the closest global catalog server.
See Microsoft KB for more information: http://support.microsoft.com/kb/319206
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. TECH179806
An error has been reported by ConfigureMsgService. It may be due to a problem contacting a Global Catalogue Server.
One or more errors occurred during the creation of a profile to connect to an Exchange Server.
Article URL http://www.symantec.com/docs/TECH139751