mailbox migration fails. User already has a primary mailbox error msg.

Anonymous
2016-06-14T11:27:55+00:00

Last week I have started to have all my new users migration from on-premises begin to fail. Using PS I get the following error below. User already has a primary mailbox already. I have tried removing the user and creating again as new on multiple user but continue to receive the error. This started sometime last week.THANKS

PS U:> New-MoveRequest -Remote -RemoteHostName webmail.paceind.com -RemoteCredential $OnPremAdmin -TargetDeliveryDom

 'paceind.com' -baditemlimit 25

cmdlet New-MoveRequest at command pipeline position 1

Supply values for the following parameters:

Identity: stephanie hintz

WARNING: When an item can't be read from the source database or it can't be written to the destination database, it

will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting that Exchange not copy such

items to the destination mailbox. At move completion, these corrupted items won't be available in the destination

mailbox.

New-MoveRequest : Target user 'Stephanie Hintz' already has a primary mailbox.

At line:1 char:16

  • New-MoveRequest <<<<  -Remote -RemoteHostName webmail.paceind.com -RemoteCredential $OnPremAdmin -TargetDeliveryDom

n 'paceind.com' -baditemlimit 25

    + CategoryInfo          : InvalidArgument: (stephanie hintz:MailboxOrMailUserIdParameter) [New-MoveRequest], Reci

   ientTaskException

    + FullyQualifiedErrorId : FC2BF0B0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

PS U:&gt;

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2016-06-14T21:26:24+00:00

    Hi Mark,

    Before the hybrid migration, the user should be a mail user in Office 365. According to the error message “Target user already has a primary mailbox”, possible cause might be that this user already has an Office 365 mailbox. So the migration fails. To troubleshooting this issue, I’d like to collect the following information.

    1. Check this user’s recipient type information.

    a. From on-premise Exchange Management Shell, run:

    Get-Mailbox UserName | fl

    b. From another PC, connect PowerShell to Exchange Online: https://technet.microsoft.com/library/jj984289(v=exchg.160).aspx. Then run:

    Get-User UserName| fl

    Get-Recipient UserName | fl

    Get-MailUser UserName | fl

    Note: replace UserName with this affected user.

    1. Try to migrate this mailbox in Office 356 Exchange Admin Center: https://technet.microsoft.com/en-us/library/o365e_hrcmoverequest_fl312271(v=exchg.150).aspx

    Do you get the same error?

    1. About “I have tried removing the user and creating again”, do you mean you have tried permanently removed the Office 365 user from recycle bin?

    Remove-MsolUser -UserPrincipalName *** Email address is removed for privacy *** –RemoveFromRecycleBin

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

    Thanks,

    Young

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2016-06-16T02:47:50+00:00

    Hi Mark,

    If you have any update, please let us know.

    *Note: On June 17th, this community is migrating to Microsoft Community at http://answers.microsoft.com. If you need further assistance, please post a new question to the Office 365 for business forum beginning June 18th Pacific Time. Thank you for your understanding.

    Thanks,

    Young

    0 comments No comments