Return
-
Title
Mage throwing sync errors because of RPCoverHTTP -
Description
Mage throws MAPI Errors, yet when checking credentials and permissions all are perfectly good.
2016-08-09 22:06:40.5573 Px578 Tx15 A21 C71 M1 Trace LdapHelper::FindOne. LDAP query: searchBase - 'LDAP://surgerypartners.net/CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=surgerypartners,DC=net', filter - '(&(cn=SXPNASSERVER03)(|(objectCategory=msExchClientAccessArray)(objectClass=msExchExchangeServer)))', username - 'surgerypartners\DMMAD3'.2016-08-09 22:06:40.5729 Px578 Tx15 A21 C71 M1 Trace Synchronize logging on to the mailbox2016-08-09 22:06:40.5886 Px578 Tx15 A21 C71 M1 Error Quest.MigrationManager.Exchange.Basis.MapiLogonException: Mapi logon failed. | at Quest.MigrationManager.Exchange.Basis.MAPISessionCreator.InternalCreateSessionAndLogon(ILdapHelper& ldapHelper, IAutodiscover& autodiscoverService, Boolean& retryLogon, String serverName, String mailboxName, String userName, String domainName, String password, CONNECT_FLAGS flags, IMapiStore& primaryStore)at Quest.MigrationManager.Exchange.Basis.MAPISessionCreator.CreateSessionAndLogon(ILdapHelper ldapHelper, IAutodiscover autodiscoverService, String serverName, String mailboxName, String userName, String domainName, String password, CONNECT_FLAGS flags, IMapiStore& primaryStore) -
Cause
It was discovered that MAgE was setup to use RPCoverHTTP to connect to the Exchange Orgs rather than MAPI, MFCMAPI confirmed that MAPI was not set working for the Exchange Orgs.
MAgE cannot make RPCoverHTTP connection.
-
Resolution
There are two options.-Add MAPI to the Exchange Orgs,-Upgrade MM to version 8.13 where MAgE can connect to the source Orgs by EWS - NOTE: that if the mailbox was already part of a collection using MAPI pre-8.13, that it will continue to use MAPI.