locked
"MigrationPermanentException: Recipient ' ' isn't a mailbox RRS feed

  • Question

  • Hi guys...!!!

    After delete the user in O365, removed from the recycle bin as well and seen if he's correctly recreated after the next DirSync cycle. The error that appears: 

    Error: MigrationPermanentException: Recipient ‎'asf.domain.mx/Auditoria Superior de la Federacion/Cuentas Usuarios ASF/50000 Auditoria Especial del Gasto Federalizado/52000 Dir Gral de Aud a los Rec Fed Transf A/Cristhian Ricardo Cazares Navarrete‎' isn‎'t a mailbox. --> Recipient ‎'asf.domain.mx/Auditoria Superior de la Federacion/Cuentas Usuarios ASF/50000 Auditoria Especial del Gasto Federalizado/52000 Dir Gral de Aud a los Rec Fed Transf A/Cristhian Ricardo Cazares Navarrete‎' isn‎'t a mailbox.

    This happened after the 1st error that appeared: "User is already being moved‎" error when you move mailboxes from on-premises to Exchange Online in a hybrid deployment.

    What else can I do?

    Thanks and Regards

    Friday, November 22, 2019 3:53 AM

Answers

  • Hi Marco,

    What’ the type of the user “Cristhian Ricardo Cazares Navarrete”? Is it a user mailbox?

    Have you check the state of the mailbox? Is it disabled?

    What’s the method you used to move the mailbox? If you used migration batche to move, you can use the following commands to verify the status of the migration batch:

    Get-MigrationBatch -Identity <batch name> | Format-List Status,Endpoint

    Get-MigrationUserStatistics -Identity <MigrationUserIdParameter> -IncludeReport | Format-List Status,Error,Report,SkippedItemCount,SkippedItems

    Please check if you have configured the settings of the “Fliter” and some attributes have been filtered out, which may resulted that you haven’t found the msExchMailboxMove* attributes.


    Regards,

    Vera Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, November 25, 2019 10:15 AM

All replies

  • Hi

    Maybe this helps:

    https://support.microsoft.com/en-us/help/4502865/cannot-move-mailboxes-from-on-premises-to-exchange-online


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, November 22, 2019 4:15 AM
  • Hi, thanks for your response

    After view the link and excecute the cmdlets Get-MoveRequest -Identity 'user@domain.com' in Exchange Server 2013 and Exchange Online appear the next message:

    • Couldn't find a move request that corresponds to the specified identity 'user@asf.domain.mx'.

    And the parameters msExchMailboxMove aren't in the AD Attibute Editor.

    Regards

    Friday, November 22, 2019 3:31 PM
  • Hi Marco,

    What’ the type of the user “Cristhian Ricardo Cazares Navarrete”? Is it a user mailbox?

    Have you check the state of the mailbox? Is it disabled?

    What’s the method you used to move the mailbox? If you used migration batche to move, you can use the following commands to verify the status of the migration batch:

    Get-MigrationBatch -Identity <batch name> | Format-List Status,Endpoint

    Get-MigrationUserStatistics -Identity <MigrationUserIdParameter> -IncludeReport | Format-List Status,Error,Report,SkippedItemCount,SkippedItems

    Please check if you have configured the settings of the “Fliter” and some attributes have been filtered out, which may resulted that you haven’t found the msExchMailboxMove* attributes.


    Regards,

    Vera Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, November 25, 2019 10:15 AM
  • Thanks for your comments...

    But, I had to backup the user information (.PST file) and delete the user from O365 using powershell to also remove it from the recycle bin.

    After, I deleted the user from Exchange Server and create the account again. I forced the synchronization with Azure AD Connect and assign the license.

    Finally, I moved the mailbox again and the user is completely in O365 with all the attributes

    Regards...!!!

    Tuesday, November 26, 2019 4:28 PM
  • I'm glad you have solved the problem and shared your solution. The following is a brief summary of this issue so that others can get help from your approach.

    Issue Symptom
    ==========================================
    After delete the user in O365, removed from the recycle bin as well and seen if he's correctly recreated after the next DirSync cycle. The error that appears: MigrationPermanentException: Recipient “…” isn‎'t a mailbox. 

    Then get the erro when you move mailboxes from on-premises to Exchange Online in a hybrid deployment: "User is already being moved‎"

    Possible Cause
    ==========================================
    Need to force the synchronization with Azure AD Connect and assign the license.

    Solution
    ==========================================
    Force the synchronization with Azure AD Connect and assign the license.

    Regards,

    Vera Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, November 29, 2019 11:35 AM