Exchange 2010 Failed to reset the target mailbox after the move.

I am migrating from Exchange 2003 to Exchange 2010.
When using Exchange 2010 EMC to do a local move request from the Exchange 2003 server in the child domain to the Exchange 2010 server in the parent domain, the move request status is Completed With Warning.

The log shows:
6/22/2015 3:23:57 PM [CityEX3] Move has completed and final clean up has started.
6/22/2015 3:23:58 PM [CityEX3] Source mailbox 'Primary (1c49f839-a808-40c0-866a-1d7058ee6fdb)' was successfully cleaned up after the move.
6/22/2015 3:23:58 PM [CityEX3] Failed to reset the target mailbox after the move. Attempt 1/6.
Error details: MapiExceptionWrongServer MapiExceptionWrongServer: Unable to open mailbox "/o=City of Fairbanks/ou=First Administrative Group/cn=Recipients/cn=jathayer" on server "CITYEX3.ci.fairbanks.ak.us". (hr=0x80004005, ec=1144)

The mailbox seems to work OK otherwise.
Please note that either the Exchange group listed shows the legacy 2003 group location while the server named is the new 2010 server.
They don't belong together.

thanks,
John
FBXITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amit KumarCommented:
As long as if you are able to open mailbox in Exchange 2010 OWA/Outlook and able to send/receive mails then you can ignore this warning. It occurs sometime due to replication or sometimes could not flush cache of source server. But it get cleaned up after sometime during online maintenance.

Also I would like to know what is SP level with RU of Exchange 2010.
0
FBXITAuthor Commented:
Exchange Server 2010 SP3 RU 9
0
Amit KumarCommented:
Then we can't say it is bug, As per my knowledge it was sought of bug in RU2/RU3 as well. Do one more thing, move it to another DB on exchange 2010 only see if warning comes again. But do AD force replication before movement.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AmitIT ArchitectCommented:
What Antivirus on user machine? Check, if there are any add-in installed in user outlook, disable and check again.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.