Event ID 2270 during archive run (0x8004010F)

Problem

During the Archive task run, the error below is logged.

Error Message

Type: Warning
Event: 2270
Source: Enterprise Vault
Category: Archive Task
Computer: EV1
Description:
A queued operation exceeded the retry count and has been discarded
Exchange Mailbox Archiving Task for Exch1
Synchronising mbx. Legacy mbx DN: [/o=EV/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=John Doe], AD mbx DN: [CN=Doe John,OU=TerminatedEmployees,DC=ad,DC=dc1,DC=com], AD msg store DN: [CN=ExchDB1,CN=ExchSG13,CN=InformationStore,CN=DB3,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=IN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ad,DC=dc1,DC=com], sync mode: [POLICIES, MAILBOX (0x3)], retry count: [3].

Error: [0x8004010F]
V-437-2270

Cause

The hex code 0x8004010F in the Event translates to: MAPI_E_NOT_FOUND or Object Not Found

This occurs when there is no longer an Exchange mailbox associated with the archive and Enterprise Vault is unaware of this. 

When a mailbox is deleted before disabling the user for archiving, it will cause the Directory Database to become inconsistent and not update properly.  The ExchangeMailboxEntry table has a column called MbxExchangeState.  When this column is not properly updated, it will exhibit this symptom.  

Solution

The entries in the ExchangeMailboxEntry table must be removed from the table. 

Note: Confirm there is a backup of the EnterpriseVaultDirectory Database prior to this change.

1. Make note of the affected user based on the Event error

2. Run the query below:

Use EnterpriseVaultDirectory
Select * from ExchangeMailboxEntry where mbxalias = 'enter alias here'

3. When the entry is found and confirmed it is the correct user, it can then be deleted by using the query below:

Use EnterpriseVaultDirectory
delete from from ExchangeMailboxEntry where mbxalias = 'enter alias here'

Note that it is also possible to run other queries to determine a group of affected users. For example. In the Event above, this affected an AD OU called TerminatedEmployees.  A sample script below can be used to identify all users in this table belonging to this same OU:

Use EnterpriseVaultDirectory
Select * from exchangemailboxentry where admbxdn like ‘%terminated%’

With the results from this query, it is now possible to run a delete against the entire set of affected users in one sweep.

4. Once all users have been cleaned out of the table, the archive task should no longer log the errors.