An error occurred while running ExchangeAutoDiscovery during ExchangeCollection. Status code 3.

book

Article ID: 100046927

calendar_today

Updated On:

Description

Error Message

<< Job Status log >>
An error occurred while running ExchangeAutoDiscovery during ExchangeCollection. Status code 3.

 

Cause

The Source Account mailbox information is not present in the local Active Directory.

If the Azure exchange information is not present in the local Active Directory servers. The primary email address (mail=) AD attribute cannot be determined, which must be present in order to discover/collect from eDP/Clearwell.

This is accomplished through running the Azure AD Connect > Azure Synchronization Service.

 

Resolution

There are two methods to determine if the needed mail attributes are present in Active Directory.

Method 1:

A. Run LDP.exe from the eDP server. (Start > Run > ldp.exe)
Note:  LDP is not installed by default. 
To install:
Open Server Manager dashboard > Add roles and features > Next > Role-based or feature-based installation > select the eDP server > select 'Active Directory Lightweight Directory Services' > Add features > Next, Next, Next, Install
-- This does not require a server reboot to be available.

B. Select Connection > Connect
Server: < insert the AD server Netbios, FQDN or IP address >
Port 389 (default) or 636

This will reply with a successful connection to the AD server:
Established connection to
 

C. Select Connection > Bind
If logged into the eDP/Clearwell server as a Domain Administrator account, use the 'Bind as currently logged on user'.  Other wise select 'Bind with credentials ands supply the logon information for a Domain Administrator account.

This will reply with a successful binding:
Authenticated as: <'Admin Account'>.
 

D. Select Browse > Search > Run
Base DN: < Top listing >  Ex: DC=eDP, DC=lab
Filter: (name=)
Scope: Subtree
Attributes: *


Note:  Other Filters: can be, but not limited to:
(sn=)
(displayName=)
(mail=)


E. The attribute information that Azure supplied to the local Active Directory will look similar to:
mail: taccount@veritas.onmicrosoft.com;
mS-DS-ConsistencyGuid: ;
msDS-SupportedEncryptionTypes: 0x0 = ( );
msExchArchiveGUID: ;
msExchArchiveStatus: 1;



Method 2:

1. Inspect the emails assigned to this failing Source Account thru the All Cases > Employee List....  is the email with the numeric extension present ?
    
2. Setup a DEBUG logging
        Property browser:
    esa.common.logger.adapter = DEBUG
    esa.common.rootlogger.ADSCrawler   = DEBUG,ADCrawlerFile

    
        System > Logs > Settings> debug level logging enabled:
    log4j.category.com.teneo.esa.common.core.ExchangeMailbox
    log4j.category.com.teneo.esa.common.partm.ParticipantsManagerImpl
    log4j.category.com.teneo.esa.directory.ads.ADSIndexer
    log4j.category.com.teneo.esa.directory.ads.ActiveDirectoryService

    
3. Run a full Active Directory synchronization
    Set esa.employeemanager.directory.sync.crawler.enablefullsync property to True, through Property Browser.
    
4. Search for the Source Account name in the server log..... did it skip that person, did it modify the email address....etc.... ?

Error: If Active Directory does not contain the Azure mail attributes needed:
2019-12-06 14:35:23,423 DEBUG [directory.ads.ADSIndexer] (ADIndexer:) CaseName:[] UserName:[] Email Address is empty. Dropping participant record for DN <0365 Source Account Information>
 

 

Issue/Introduction

When attempting to collection from the o365 Exchange environment, the eDP Collection Task fails during the AutoDiscovery phase of the task.