Mail is not synchronizing to Exchange 2013 and upon review of the MAgE (Migration Agent for Exchange) log the following error is displayed.
System.DirectoryServices.DirectoryServicesCOMException (0x80072030): There is no such object on the server.
A review of the 3 lines above the error will give a bit more information as to where the MAgE is trying to access to find the mailbox.
M2 Info Quest.MigrationManager.Exchange.Basis.LdapHelper.domain: GC at 'targetdomain.com' is ready, will use it.
M2 Trace LdapHelper::FindOne. LDAP query: searchBase - 'GC://targetdomain.com', filter - '(&(objectClass=person)(legacyExchangeDN=/O=domain/OU=CT/cn=Recipients/cn=usermailbox))', username - 'targetdomain\target_service_account'.
M2 Trace LdapHelper::FindOne. LDAP query: searchBase - 'LDAP://domain.com/CN=EC Mailbox Store 2,CN=EC_SG,CN=InformationStore,CN=EX1,CN=Servers,CN=CT,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com', filter - '(&(objectClass=msExchPrivateMDB))', username - 'domain\target_service_account'.
We can see in the top line MAgE is looking in the targetdomain.com domain. In the 2nd line the MAgE is looking for the object (usermailbox). Then in the 3rd line the MAgE is looking where to find it. We can also see by the targetdomain\target_service_account the identity that the MAgE is using to connect to Active Directory.
So to resolve the error message Full Control on CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain of the organization> will need to be granted for the service account.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center