Provisioning Task: Mailbox in different domain not processed

book

Article ID: 100007354

calendar_today

Updated On:

Description

Error Message

Then DTrace the EvExchangePolicySyncTask process, search for the term exception in the logs.

{EXCHANGEPOLICYSYNCHRONIZATION.EN_US} Exception raised for user [CN=Joe Bloggs, OU=Accounts,OU=Enterprise Vault,OU=Services,DC=test,DC=net] in provisioning group [Test Mailbox Archiving] / [TEST\EV Mailbox Archiving] - Exchange server [CN=Exchange01,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Test Group,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=test,DC=net] is not part of the domain. Stack trace:    at KVS.EnterpriseVault.ExchangePolicySync.ExchangePolicySynchronization.GetExchangeServerID(String mailboxDatabase)|   at KVS.EnterpriseVault.ExchangePolicySync.ExchangePolicySynchronization.UpdateMailboxEntry(UserProperties userProps, PolicyTargetInfo targetInfo, ExchangeMailboxEntry mbxEntry, Int32 storeID, Boolean bRelink)|   at KVS.EnterpriseVault.ExchangePolicySync.ExchangePolicySynchronization.ProcessCreateOrUpdateMailboxEntry(UserProperties userProps, PolicyTargetInfo targetInfo)|   at KVS.EnterpriseVault.ExchangePolicySync.ExchangePolicySynchronization.WorkerThreadFunc()
 

Run AdsiEdit.exe to view the directory structure of the Domain in Active directory and locate the user. Check the full path for the user, here is an example,

[CN=Exchange01,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Test NET,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=test,DC=net]

You can also verify this by checking the LegacyMbxDN in SQL for the Exchange target:

SELECT * FROM ExchangeServerEntry

CN=EXCH9,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Test Group,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=knox9,DC=com

The problem is the CN=Test Group, which is being used within the EnterpriseVaultDirectory Database.

Cause

EV is determining that the mailboxes are in a different domain. This is usually caused by a change to the Active Directory structure or the target Exchange Servers have indeed been moved to a new domain.

Resolution

The solution is to remove and re-create the Exchange targets.

To do this follow these steps.

  1. Follow https://www.veritas.com/docs/000029085 to make sure that the MSMQ's are empty.
  2. Stop the Storage server and all of the archiving and provisioning task.
  3. Make a note of all of the configuration options for the Tasks, as well as the Exchange targets, Public Folder and Journal settings as you will need this information to re-create them.
  4. Delete the Exchange Target within the Enterprise Vault Admin Console (Site > Targets > Exchange > Domain > Exchange Server).
  5. Delete the MSMQs for each Exchange server.
  6. Create a New Exchange Target and follow the wizard (Site > Targets > Exchange > Domain > Exchange Server), to re-create the tasks and MSMQs.
  7. Check that you can run the Provisioning Task and synchronise all mailboxes.
  8. Restart the Archiving tasksx

Issue/Introduction

When running the Provisioning task the following can be seen within the report generated for some users. Mailbox not processed as located in an Exchange mailbox database that is not in the current domain or on an Exchange Server that has not been added as a target Enabling and disabling new mailboxes may fail along with Archiving and Synchronisation.