locked
Exhange 2013 - Error Message on Succesful Migration of Mailboxes RRS feed

  • Question

  • Hi

    I'm getting a message when ever I do a mailbox migration. I have tried searching on the web for clues as to what could be causing this but have currently drawn a blank.

    I have migrated from one exchange 2013 server to another exchange 2013 server.

    All of the system, discovery and public folder mailboxes has successfully been moved over to the new server.

    Old server was a physical server. New server is on a VM on hyper-v

    No DAG is configured.

    Mailbox moves complete successfully but the error appears.

    The error is.

    THE SUBSCRIPTION FOR THE MIGRATION USER X@X.COM COULDN'T BE LOADED. THE FOLLOWING ERROR WAS ENCOUNTERED: MAILBOX 'X' IS NOT CURRENTLY BEING MOVED..

    Was wondering what the issue is and how I resolve it.

    Mailbox moves do seem to be taking place fine. But this even happens when you move mailboxes between databases on the same server.

    Cheers

    Blue

    

    Wednesday, May 6, 2015 9:27 AM

Answers

  • Hi,

    According to your post, I notice that move mailbox between database within same server failed.
    If I misunderstand your concern, please do not hesitate to let me know.

    I want to double confirm whether all mailbox moving or some special account experience this question.
    Besides, we need more detail error message for troubleshooting. Please review the Event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
    Here’s an article about “Troubleshooting Mailbox Moves”, for your reference: https://technet.microsoft.com/en-us/library/dd638094%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396

    Thanks


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    • Marked as answer by Allen_WangJF Tuesday, May 19, 2015 1:26 PM
    Friday, May 8, 2015 9:38 AM

All replies

  • Hi Blue,

    Run Setup /prepareAD again on the server and check.

    Also use Remove-MoveRequest or MigrationBatches to clear the requests if any.

    Do you have any O365 mailboxes involved.

    References:

    https://social.technet.microsoft.com/Forums/exchange/en-US/127a11c0-ef8c-45b9-97e7-b336218cd2a1/exchange-2013-move-mailbox-warning-could-not-load-the-subscription-for-migration-user?forum=exchangesvrgeneral

    Unable to provision jobs from the current recipient. The owner recipient isn't a valid user.


    Regards,

    Satyajit

    Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Wednesday, May 6, 2015 11:31 AM
  • Hi

    Thanks for getting back....

    Take it I run preparead using exchange cu8...

    Also will it have any bad affect on the existing ad\exchange?

    cheers

    Wednesday, May 6, 2015 2:52 PM
  • And no...no office 365...

    was first exchange server 2013 to exchange server 2013...

    and then it was between databases on the same exchange server..

    it completes but just gives the error message during the migratoin and when you click on the item..

    Wednesday, May 6, 2015 2:55 PM
  • Hi Blue,

    CUs are meant to be run on existing servers unless its a fresh install,  hence no it will not have any bad effect on the existing infra provided you have read the Release notes (known issues) for anything mentioned that might pertain to your environment.

    Ideally you should take the servers on Maintainance mode prior to patching.

    According to this, there are no new schema changes present in CU8.  If upgrading from CU6 or older then AD schema changes will still need to be applied to update to the CU7/CU8 level.

    References:

    Exchange 2013 CU8 Released


    Regards,

    Satyajit

    Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Thursday, May 7, 2015 6:31 AM
  • Hi 

    Thanks...

    Will be doing this at a later date, so will def come back to this. They got me looking through the event viewer and other projects since it doesn't seem to be adversly affecting the system.

    Thursday, May 7, 2015 9:55 AM
  • Hi 

    Going down the rabbit hole is getting strange.

    Tried it from the actual server using ie and no error and could download the user migration report

    Tried it from my pc, chrome and ie in safe move no error and could donwload the user migration report

    Deleted the browsing history on ie on my pc, - but still the same problem....Strange...


    Thursday, May 7, 2015 10:14 AM
  • Hi,

    According to your post, I notice that move mailbox between database within same server failed.
    If I misunderstand your concern, please do not hesitate to let me know.

    I want to double confirm whether all mailbox moving or some special account experience this question.
    Besides, we need more detail error message for troubleshooting. Please review the Event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
    Here’s an article about “Troubleshooting Mailbox Moves”, for your reference: https://technet.microsoft.com/en-us/library/dd638094%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396

    Thanks


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    • Marked as answer by Allen_WangJF Tuesday, May 19, 2015 1:26 PM
    Friday, May 8, 2015 9:38 AM