The following errors may be encountered in the Migrator for Notes to Exchange (MNE) migration log file:
ERROR: [4965-24-45-8004011D] Unable to open target mail store
OpenMsgStore:
MAPI error 8004011D
The sample error above is a generic Microsoft MAPI connection error that has many possible causes. MAPI error 8004011D can mean anything from the username/password is not correct for the Exchange migration admin account, to network connectivity was lost with Exchange or Office 365.
The error above may be followed by additional information about the cause of the error, when it is available:
CAUSE 1: Exchange login issue:
Error: The attempt to log on to Microsoft Exchange has failed.
Component: Microsoft Exchange Information Store
Low level error: 80040126
Context: 00000512
CAUSE 2: Exchange/Office 365 network connectivity issue:
Error: Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.
Component: Microsoft Exchange Information Store
Low level error: 80040115
Context: 00000526
RESOLUTION 1
Verify the Exchange/Office 365 credentials MNE is using by following this procedure:
1.) Open the MNE Migration Manager.
2.) Click on the Exchange Server settings screen on the left hand pane.
3.) Re-enter the Administrator domain\username or user principal name field.
4.) Re-enter the Administrator password.
5.) Click the Apply button.
6.) Retry the migration.
Note: If the migration still fails, then you may want to change the Administrator username to a UPN (ex. user@domain.com). If the Administrator username was already entered as a UPN, then try the "DOMAIN\User" format.
MNE creates MAPI profiles on the fly during the migration. Under certain circumstances these auto-generated MAPI profiles can be left behind. The following steps will remove these MAPI profiles:
1. Open the Mail Control Panel
2. Click Show Profiles.
3. MNE created profiles appear with the following pattern "~EXCHFB-XXXXXXX-0"
4. Highlight the first (top) profile in the list that follows the naming pattern above.
5. Hold down "ALT" on the keyboard and alternate pressing "E" then press "Y".
6. If you continue to hold down "ALT" and alternate pressing "E" then "Y", the profile deletion process should go relatively quickly.
RESOLUTION 2
On-Premise Exchange migrations:
The following partial list of conditions could cause this error:
a.) Configuring the MNE migration server to go through a load balancer or firewall to get to Exchange.
b.) Intermittent network connectivity issues between the MNE migration server and Exchange.
c.) Exchange server unavailable due to Windows Updates or other scheduled maintenance.
d.) Exchange throttling policies.
e.) Running multiple MNE migration servers with a cumulative total of simultaneous threads greater than 32. This issue is separate from Exchange throttling policies. See the following KB article for more details:
ERROR: [4970-24-52-8004011D] Unable to open mailbox for user 'UserA@domain.com'
Office 365 Migrations:
The following partial list of conditions could cause this error:
a.) Configuring the MNE migration server to go through an Internet proxy server or WAN accelerator to reach the Internet.
b.) Intermittent connectivity issues between the MNE migration server and the Internet and on to Office 365.
c.) Office 365 scheduled maintenance or service outages. Login to your Office 365 tenant portal and check the Dashboard.
d.) Permissions propagation delay in Office 365. See the following KB article for additional information:
Migrator for Notes to Exchange (MNE):
Migrator for GroupWise (MFG):
e.) April 2015: Recent changes in Office 365 have required the Admin Pool accounts to be licensed Office 365 users. Migrator for Notes to Exchange (MNE) 4.12.1.21 has been released with new functionlity to automatically license the Admin Pool accounts, if necessary.
f.) July 2015: Recent changes in Office 365 seem to be causing MAPI connections to drop intermittently. Adding the following parameter to the MNE Global Default Settings should allow MNE to restart the migration automatically should this issue occur:
[Exchange]
MapiErrorsToRetry=80040115,80040125,8004011D
Note: These retries will use the same MAPI session and "RPC Token". They might not cure the problem that may be of a result of communication and connectivity issues. Once all retries have failed, MNE will restart the process which starts a complete new worker process, which will create a new MAPI connection and session.
