Troubleshoot Active Migration Errors

Applies to: Office 365 for professionals and small businesses, Office 365 for enterprises, Live@edu

Topic Last Modified: 2012-06-26

After you start a migration batch, Exchange Online logs any errors that occur during the migration. These errors are listed in the error report for the migration batch. To display this report, select My Organization > Users & Groups > E-Mail Migration, and then select a migration batch in the migration batch list. Under Reports in the right-hand pane, click Error, and then download the migration error report. This error report is also attached to the status e-mail message sent after the migration batch is complete.

What happens when migration errors are found?

Errors found after you start a migration batch prevent the affected mailboxes from being migrated. You have to wait until the current migration batch is done before you can fix these errors. Then you can create a new migration batch or re-start an existing batch.

Cutover Exchange migration errors

The following table describes common errors for cutover Exchange migrations and suggested solutions.

Error	Suggested solutions
Couldn't connect to the source mailbox	Verify that the migration administrator is assigned Receive-As permissions to the mailbox database or Full Access permissions to every mailbox. Create a new account to use as the migration administrator, and then assign Receive-As permissions to the mailbox database to this account or Full Access permissions to every mailbox. Create a new mailbox database in the on-premises organization, and then move all mailboxes to this new database.
A source e-mail address <user e-mail address> couldn't be found in the on-premises domain.	Verify that the user isn’t hidden in the on-premises address list. If the user is hidden, clear the Hide from Exchange Address lists checkbox on the user’s properties page in the Exchange Management Console, and then re-run the migration.

Error

Suggested solutions

Couldn't connect to the source mailbox

Verify that the migration administrator is assigned Receive-As permissions to the mailbox database or Full Access permissions to every mailbox.
Create a new account to use as the migration administrator, and then assign Receive-As permissions to the mailbox database to this account or Full Access permissions to every mailbox.
Create a new mailbox database in the on-premises organization, and then move all mailboxes to this new database.

A source e-mail address <user e-mail address> couldn't be found in the on-premises domain.

Verify that the user isn’t hidden in the on-premises address list. If the user is hidden, clear the Hide from Exchange Address lists checkbox on the user’s properties page in the Exchange Management Console, and then re-run the migration.

Staged Exchange migration errors

The following table describes common errors for staged Exchange migrations and suggested solutions.

Error	Suggested solutions
A valid primary e-mail address couldn't be found in the cloud-based service.	Verify that the Microsoft Online Services Directory Synchronization tool created a mail user object in your cloud-based organization. Verify that the e-mail address used in the migration CSV file is the same as the primary SMTP address for the corresponding mail user in your cloud-based organization. Both addresses should match the primary SMTP address for the on-premises mailbox.
A source e-mail address <user e-mail address> couldn't be found in the on-premises domain.	Confirm that the on-premises mailbox exists. Verify that the e-mail address in the CSV file is the same as the primary SMTP address of the on-premises mailbox. Verify that the user isn’t hidden in the on-premises address list. If the user is hidden, clear the Hide from Exchange Address lists checkbox on the user’s properties page in the Exchange Management Console, and then re-run the migration.
Microsoft Exchange couldn't sign in to the user’s on-premises account.	Verify that the administrator account has the necessary permissions to access the on-premises mailbox database or specific user account. Confirm that the account still exists. Verify that you're using the correct user name and password (if included) for the account in the CSV file. If you're using an administrator account with super-user credentials: Verify that you're using the correct user name and password for the administrator account in the CSV file. Verify that you're using the correct user name for the user account in the CSV file.
A Windows Live error occurred while provisioning for <user e-mail address>. An internal error occurred while talking to Windows Live. Additional details: "0x800482101033 This action is currently blocked for the API".	If you’ve implemented single sign-on by deploying Active Directory Federation Services 2.0 in your on-premises organization, you must use `False` for the value of the ForceChangePassword attribute in the migration CSV file. If you’ve used the `True` value for this attribute, change it to `False` and then resubmit the CSV file. Alternatively, you can remove the Password and ForceChangePassword columns from the CSV file.

IMAP migration errors

The following table describes common IMAP migration errors and suggested solutions.

Error	Suggested solutions
Microsoft Exchange couldn't sign in to the user account on the IMAP messaging system.	Confirm that the account still exists. Verify that you're using the correct user name and password for the account in the CSV file. If you're using an administrator account with super-user credentials: Verify that you're using the correct user name and password for the administrator account in the CSV file. Verify that you're using the correct user name for the user account in the CSV file. Verify that the administrator account has the necessary permissions to access the on-premises mailbox database or specific user accounts.
A cloud-based mailbox wasn't found for the user.	Confirm that the cloud-based mailbox exists. If it doesn't, create a cloud-based mailbox for the user. Verify that you're using the correct e-mail address for the user's cloud-based mailbox.
The user's mailbox has already been migrated.	If you run a new migration batch, in the CSV file, remove the rows for mailboxes that have already been migrated.
Microsoft Exchange couldn't connect to the IMAP server.	Verify that the IMAP service is running on the IMAP server. Verify that the IMAP server is available and that you can connect to it. Tip Use an IMAP client to connect to the IMAP server. Use the same connection settings that you used when you ran the migration batch. Or use the PING command to test whether you can communicate with the IMAP server.
The user's cloud-based mailbox is full.	Free up space in the user's cloud-based mailbox.

Use the MigrationErrors.csv file to troubleshoot and fix migration errors

Use the information in the E-mail Migration Per-User Status Report or the MigrationErrors.csv file to identify and fix errors. Use the error information to resolve the problem that caused a row to fail. Then create and start a new migration batch, or edit an existing migration batch, and submit a revised CSV file that contains the rows that have been fixed.

For more information, see E-Mail Migration Users Status Report.