-
Title
NM: Warning connecting to default folder: Error in IMAPISession::OpenMsgStore: MAPI_E_LOGON_FAILE -
Description
NM: Warning connecting to default folder: Error in IMAPISession::OpenMsgStore: MAPI_E_LOGON_FAILE -
Resolution
Issue
We had migrations running successfully, and now migrations are failing. We added more migration workers to the migration farm.
Why are we receiving these errors in the verbose log?
@ 20:22:01 Calling autodiscover application: "C:\Program Files (x86)\Binary Tree\CMT for Exchange\Worker\OutlookAgent32.exe" -address user@domain.com -user "MigrationAdmin@domain.com" -password "*********" -type mailbox -profile "CMT Temp Migration Profile" -l "C:\Users\MigrationAdmin.GMX\AppData\Local\Binary Tree\Notes Migrator\BTautodiscover.log"
@ 20:22:27 Begin AutoDiscover and Profile Creation Log
20:22:27 8:22 PM: [Info] Using Exchange credentials from registry
20:22:27 8:22 PM: [Info] Logging in with: migrationadmin@domain.com
20:22:27 8:22 PM: [Warning] Warning connecting to default folder: Error in IMAPISession::OpenMsgStore: MAPI_E_LOGON_FAILED
20:22:27 Make sure your code runs under the Windows user identity that has MAPI profiles.
20:22:27 When running in a service (including ASP under IIS), set your code to run under
20:22:27 the Windows user account that has MAPI profiles.
20:22:27 When connecting to an Exchange Server, you can also use RDOSession.LogonExchangeMailbox
20:22:27 which does not require an existing profile.
20:22:27 ulVersion: 0
20:22:27 Error: The information store could not be opened.
20:22:27 Component: MAPI 1.0
20:22:27 ulLowLevelError: 0
20:22:27 ulContext: 646
20:22:27 8:22 PM: [Error] Unable to logon to Hosted Exchange Mailbox:Solution
Confirm there is no throttling policy in Exchange which limits the number of connections for a mailbox account. This is the most like reason.
Confirm you are using multiple accounts for the migration ids, to adhere to the throttling policy, or increase the number of concurrent connections.
If this is not the issue, then confirm the following:
Run the connectivity tester again, and confirm the credentials are correct. Is this for a single user or many? If a single user, then it's not the migration account. Confirm the migration account is listed as having Full Access to the user's target mailbox, and this mailbox is MAPI enabled. Confirm Outlook Anywhere is configured for this user. Confirm the migration account can open this user's mailbox from the migration workstation.
If all this is correct, have they tried migrating to a different machine.
When was the user's target mailbox provisioned, created, and migration run? Was there at least 15 minutes between the creation and the migration run, giving the target servers ample time to synchronize?
What is different about this user vs other users?
If this is all migrations, then make sure the cloud autodiscover IP is placed in the migration hosts file.Contact Binary Tree support if this does not resolve the issue support@binarytree.com