-
Title
Error MigrationManager.Exchange.Basis.MapiLogonException: Mapi logon failed. | at MigrationManager.Exchange.Basis.MAPISessionCreator.InternalCreateSessionAndLogon(ILdapHelper& ldapHelper, IAutodiscover& autodiscoverService, Boolean& retryLogon, String -
Description
MAGE can't perform a MAPI logon to a mailbox on Exchange 2007 with the error below:Info MAPI logging on to the mailbox : /o=[source_organization]/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=test.user (server : [source_server_name], user: [service_account], connection flags: aeCONNECT_EMPTY)Error MigrationManager.Exchange.Basis.MapiLogonException: Mapi logon failed. | at 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 MigrationManager.Exchange.Basis.MAPISessionCreator.CreateSessionAndLogon(ILdapHelper ldapHelper, IAutodiscover autodiscoverService, String serverName, String mailboxName, String userName, String domainName, String password, CONNECT_FLAGS flags, IMapiStore& primaryStore)at MigrationManager.Exchange.Agent.Jobs.O365Job.get_MapiSession()at MigrationManager.Exchange.Agent.Jobs.O365Job.get_MapiStore()at MigrationManager.Exchange.Agent.Jobs.O365Job.InitSource(Boolean isFirstSession, ISmtpResolver smtpResolver)at MigrationManager.Exchange.Agent.Jobs.O365Job.InitSourceTarget(Boolean isFirstSession)at MigrationManager.Exchange.Agent.Jobs.O365Job.BeforeSync()at MigrationManager.Exchange.Agent.Jobs.DisPlusO365JobBase.RunJob()[inner] System.Runtime.InteropServices.COMException: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. - MAPI_E_FAILONEPROVIDER (Microsoft Exchange Server Information Store) Low level error: 0x0 File: 'aeWrapHelpers.h' Line: '279' |Server stack trace:at Quest.MigrationManager.Exchange.Interop.aeEMWMageLib.aeMAPISessionClass.Logon(String ServerName, String MailboxName, Object UserName, Object DomainName, Object Password, CONNECT_FLAGS flags)at MigrationManagerForExchange.General.MAPI.aeMAPISessionWrapped.Logon(String ServerName, String MailboxName, String UserName, String DomainName, String Password, CONNECT_FLAGS flags)at MigrationManagerForExchange.General.MAPI.IMapiSession.Logon(String ServerName, String MailboxName, String UserName, String DomainName, String Password, CONNECT_FLAGS flags)at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)MFCMAPI can't log on to this mailbox with MAPI_E_FAILONEPROVIDER error. -
Cause
Mailbox database where problem mailbox is homed has got a Public Folder database associated with it, however, no Public Folder databases exist in the Exchange organization. -
Resolution
MAGE uses different flags to perform MAPI logon in cases when Public Folder database(s) exist in the Exchange organization and when no Public Folder database(s) are present.
If private mailbox database has no Public Folder database associated to it, MAGE uses connection flag aeCONNECT_IGNORE_NO_PF. In this case msExchHomePublicMDB attribute value of the private mailbox database is <not set>.
If private mailbox has got an associated Public Folder database, it uses connection flag aeCONNECT_EMPTY. In this case msExchHomePublicMDB attribute value of the private mailbox database is set to the DN on the associated Public Folder database.
This flag can be seen in the log trace showing logon:
MAPI logging on to the mailbox : /o=[source_organization]/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=test.user (server : [source_server_name], user: [service_account], connection flags: aeCONNECT_EMPTY)
If Public Folder database doesn't exist in the Exchange organization, but the msExchHomePublicMDB attribute value of the private mailbox database is populated, the MAGE uses aeCONNECT_EMPTY flag when logging on, but fails because no Public Folder database actually exists.
To resolve the issue, clear msExchHomePublicMDB attribute of the mailbox database and resynchronize the problem mailbox.