Richie Knight
asked on
Exchange 2010 Migration to Office 365 using Code Two - The specified object was not found in the store
Hi all.
We are in the process of doing an Exchange 2010 migration to Office 365 using the Code Two Office 365 Migration Tool. Although many of the mailboxes have moved over fine, we are getting quite a few that are not with the below error.
The specified object was not found in the store., Can't connect to the mailbox of user Mailbox database guid: *********-****-****-****-*
Could someone please advise on what could be going wrong?
Thank you.
We are in the process of doing an Exchange 2010 migration to Office 365 using the Code Two Office 365 Migration Tool. Although many of the mailboxes have moved over fine, we are getting quite a few that are not with the below error.
The specified object was not found in the store., Can't connect to the mailbox of user Mailbox database guid: *********-****-****-****-*
Could someone please advise on what could be going wrong?
Thank you.
ASKER
Hi CodeTwo Support.
Yes we have a ticket raised and are waiting to be contacted but this migration is time sensitive and we need to get things working now.
Many thanks,
Yes we have a ticket raised and are waiting to be contacted but this migration is time sensitive and we need to get things working now.
Many thanks,
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Timgreen7077 - The mailbox still exists in the database.
CodeTwo - I am calling back now.
Many thanks,
CodeTwo - I am calling back now.
Many thanks,
ASKER
Well it seems that the Exchange GUID for each of the failed mailboxes is changing causing a mismatch. CodeTwo have been kind enough to get us setup with another instance of the software running on one of our other servers. We are going to start by deleting the failed accounts in 365 and syncing them from the other server. Although this should work, I am somewhat nervous as if they change again we will be in the same situation again. This is quite time consuming.
good luck.
ASKER
Running a rescan many times seems to have finally allowed the migration to complete. It appears that whilst the mailboxes are in use, the GUID error appears. Performing the rescan whilst the users were logged out resulted in successful completion.
Thanks for your help guys.
Thanks for your help guys.
Have you contacted our technical support? The Support Team is available 24/5 and will be glad to assist you with any technical issues you might have. You can use this form to contact us.