Please enter search query.
Search <product_name> all support & community content...
Exchange Provisioning Task Report - Mailbox not processed as located on an Exchange Server that is not in the current domain
Article: 100019788
Last Published: 2026-01-07
Ratings: 1 0
Product(s): Enterprise Vault
Problem
Exchange Provisioning Task Report - Mailbox not processed as located on an Exchange Server that is not in the current domain
Error Message
Mailbox not processed as located on an Exchange Server that is not in the current domain
Solution
Some Mailboxes are not provisioned and can not be enabled for archiving, however newly created mailboxes can be provisioned
The Provisioning Task Report shows the following:
Identifying the error:
1. Perform Dtrace against the EvExchangePolicySyncTask
Notes:
a. For instructions on using the DTrace.exe tool, see Related Documents
b. Perform a Run Now on the Provisioning Task to record the error.
Dtrace Log:
Using LDIFDE.EXE carry out a query against Active Directory from the Enterprise Vault server:
1. From a command prompt change directory to Windows\System32
2. In the command prompt window, type ldifde.exe -f c:\ldifdequery.txt (an output file will be created in C: called ldifdequery.txt)
3.Compare the results from a user that may be provisioned to a user that is not provisioned
Note: For additional assistance in using the LDIFDE.EXE utility, please contact Microsoft Support.
Example 1:
Active Directory Attribute for user that is not provisioned LDIFDE query output shows:
msExchHomeServerName: o=Arctera TEST EXCH ORG/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCH01
Example 2:
Active Directory Attribute for a user that is getting provisioned LDIFDE query output shows:
msExchHomeServerName: /o=Arctera TEST EXCH ORG/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCH01
When comparing these results, the user which is not provisioned is missing "/" as shown in 'Example 1'
The missing "/" is causing the user not to be provisioned
Note: If a portion of the msExchHomeServerName is incorrect, this issue will also occur.
The Provisioning Task Report shows the following:
17:45:20 1 Arctera TEST Mailbox Archive DOMAIN\Everyone in EXCHANGE Exchange Mailbox Policy Default Exchange PST Migration Policy CN=TEST\, USER01,OU=TEST USERS,DC=DOMAIN,DC=COM Mailbox not processed as located on an Exchange Server that is not in the current domain (o=Veritas TEST EXCH ORG/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCH01)
Identifying the error:
1. Perform Dtrace against the EvExchangePolicySyncTask
Notes:
a. For instructions on using the DTrace.exe tool, see Related Documents
b. Perform a Run Now on the Provisioning Task to record the error.
Dtrace Log:
{EXCHANGEPOLICYSYNCTASKPROCESSOR.EN_US} Exception raised for user [CN=TEST\, USER01,OU=TEST Users,DC=DOMAIN,DC=COM] in provisioning group [Veritas TEST Mailbox Archive] / [DOMAIN\Everyone in EXCHANGE] - Exchange server [o=Arctera TEST EXCH ORG/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCH01] is not part of the domain. Stack trace: at KVS.EnterpriseVault.ExchangePolicySync.ExchangePolicySyncTaskProcessor.GetExchangeServerID(String legacyDN)| at KVS.EnterpriseVault.ExchangePolicySync.ExchangePolicySyncTaskProcessor.CreateMailboxEntry(UserProperties userProps, PolicyTargetInfo targetInfo, Int32 storeID, String defaultVaultId, String& newMbxEntryId)| at KVS.EnterpriseVault.ExchangePolicySync.ExchangePolicySyncTaskProcessor.ProcessCreateOrUpdateMailboxEntry(UserProperties userProps, PolicyTargetInfo targetInfo)| at KVS.EnterpriseVault.ExchangePolicySync.ExchangePolicySyncTaskProcessor.WorkerThreadFunc()
Using LDIFDE.EXE carry out a query against Active Directory from the Enterprise Vault server:
1. From a command prompt change directory to Windows\System32
2. In the command prompt window, type ldifde.exe -f c:\ldifdequery.txt (an output file will be created in C: called ldifdequery.txt)
3.Compare the results from a user that may be provisioned to a user that is not provisioned
Note: For additional assistance in using the LDIFDE.EXE utility, please contact Microsoft Support.
Example 1:
Active Directory Attribute for user that is not provisioned LDIFDE query output shows:
msExchHomeServerName: o=Arctera TEST EXCH ORG/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCH01
Example 2:
Active Directory Attribute for a user that is getting provisioned LDIFDE query output shows:
msExchHomeServerName: /o=Arctera TEST EXCH ORG/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCH01
When comparing these results, the user which is not provisioned is missing "/" as shown in 'Example 1'
The missing "/" is causing the user not to be provisioned
Note: If a portion of the msExchHomeServerName is incorrect, this issue will also occur.
This issue can also occur if the Exchange Database(s) are active on an Exchange server that is not listed under
Exchange > domain_name > Exchange Server in the Vault Console.
Resolution:
The msExchHomeServerName attribute in Active Directory has missing information. Contact Microsoft Support for further assistance
Resolution:
The msExchHomeServerName attribute in Active Directory has missing information. Contact Microsoft Support for further assistance
Ensure the Exchange Database(s) are active on an Exchange server that is a part of the Enterprise Vault configuration.