Errors on last 4 mailboxes

Question

Hi All,

I am currently doing a cutover migration to o365 from exchange 2010 on prem. I have migrated 96 mailboxes and have sorted out some errors already but these last few i cant seem to find the cause.

Here are the errors, I have three mailboxes (two user and one shared) showing this

Error: MigrationMRSPermanentException: Error: MapiExceptionUnknownUser: Unable to make connection to the server. ‎(hr=0x80004005, ec=1003)‎ Diagnostic context: Lid: 49064 dwParam: 0x3 Lid: 59431 EMSMDB.EcDoConnectEx called [length=127] Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3EB][length=56][latency=15] Lid: 59505 StoreEc: 0x3EB Lid: 50544 ClientVersion: 15.1.365.24 Lid: 51056 ServerVersion: 14.3.195.4001 Lid: 52080 StoreEc: 0x3EB Lid: 51152 Lid: 52465 StoreEc: 0x3EB Lid: 60065 Lid: 33777 StoreEc: 0x3EB Lid: 59805 Lid: 52487 StoreEc: 0x3EB Lid: 19778 Lid: 27970 StoreEc: 0x3EB Lid: 17730 Lid: 25922 StoreEc: 0x3EB 

I have one mailbox showing this 

Error: ProvisioningFailedException: Uniqueness validation failed --> Uniqueness constraint violation. 

Any help would be great

Answer 1

Hi GMA4514,

I have checked the results of PowerShell and noticed that there is the error “You can't use the domain because it's not an accepted domain for your organization.”. May I know whether there are any domains only using in your old mail provider, but you didn’t verify them in Office 365? If so, please try removing them and check them again.

If the issue persists, since you mentioned the Greg mailbox is uploading now, please run the following PowerShell commands for the problematic user and provide the results via private message.

Get-MigrationUserStatistics -Identity *** Email address is removed for privacy *** -IncludeReport | FL

Best Regards,

Erick

Answer 2

1.  I found an external user account with an ...#ext# username.  Probably due to some history of inviting Greg via email to a SharePoint server site as an external user before the migration batch was created.
2. posted for accounts as representative of the 3 failing mailboxes
3.  yes the 3 shared mailbox outputs were the same.

Answer 3

Greg Mailbox is now sorted and is currently uploading

On the last three the output from powershell was the same for all three. Any ideas as to what the problem is please?

Answer 4

Hi GMA4514,

Thanks for the information. Let’s continue analyzing the migration issues?

1. About “The greg mailbox error has changed after I found and herd deleted an external user account with the same smtp address”, could you provide the detailed steps you have done?
2. Upon analyzing the PowerShell logs, I find the following error messages:

Error: ProvisioningFailedException: You can't use the domain because it's not an accepted domain for your organization.

Looks like the mailboxes’ email address suffix is not verified in Office 365 tenant, such as proxy address domain.

Could you please go to on-premise Exchange Management, and run this command to check the email address.

Get-Recipient UserName | fl

Note: replace UserName with this affected user name.

Then, please provide the entire output in private message.

3. For the 4 problematic mailboxes, did you get the same error message when running this command?

Get-MigrationUserStatistics -Identity *** Email address is removed for privacy *** -IncludeReport | FL

From your PowerShell output, it seems that you only run this command against one user.

Thanks,

Young

Answer 5

Hi GMA4514,

According to the error message, the first error is a connection issue. For the second issue, looks like the mailbox cannot be provisioned due to some conflict error. But no more detailed information can be found in the error message. May I collect some more information to troubleshoot the issue?

1. About the migration error, could you provide the entire screenshot?  
2. Use PowerShell to get the migration information.

a. Connect PowerShell to Exchange Online: https://technet.microsoft.com/library/jj984289(v=exchg.160).aspx

b. Run the following commands:

Get-MigrationBatch | fl

Get-MigrationStatistics | fl

Get-MigrationUserStatistics -Identity *** Email address is removed for privacy *** -IncludeReport | FL

Note: user@domainom is the problematic user.

3. Make sure: the on-premises admin account that you use to connect to your on-premises Exchange organization (also called the migration administrator) has the necessary permissions to access the 4 affected on-premises mailboxes. The required permission are:  member of the Domain Admins group in Active Directory, or FullAccess permission, or Receive As permission.

If the migration admin account cannot access the on-premise mailboxes, such connection errors might occur.

4. For the 4 affected mailboxes, can you see them in Office 365 admin center (Active Users) and Exchange admin center (recipients -> mailboxes)?

To protect your privacy, I have sent a private message to request the PowerShell information. Please use this link to access the private message: https://community.office365.com/user/conversations

Thanks,

Young