I have two issues when moving mailbox. Maybe someone will help me. 1. Lets imagine. I have Exchange 2010 Sp2 RU3 maibox server and I issue mailbox local move request (to move mailbox from one database to another). Both databases exist on the same server. And when I open move request properties I see strange situation. Source version is 14.2 (Build 309.0) and the target version is 14.2 (Build 247.0). Why is that? When I try to move mailbox back to original database - the result is the same. Source version is higher and target version is lower. 2. And most of the time move requests finish with the following warning: Warning: Failed to clean up the source mailbox after the move. Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) How can I correct such issue? Thanks.

Hi Question 2: I find many similar cases in this month(ru3 release). No one is sovled perfect. I test it in my environment. i also meet this warning. But the users are in soft-delete sattus. So it won't affect your production. Some customers remove whole origin database. It works for some users. TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.comTerence Yu TechNet Community Support

Question one. Looked at this thread. It only shows that I'm not the only one. But no solution at all, and no answers from Microsoft at all about this:( Question 2. Looked at the application log. I can see the following things: 1. Warnings that user is not able to login as mailbox is in move status. 2. Error: Failed to delete the mailbox of 3ded0fba-15ce-47d2-80f1-2f3d5ba0d644 with error 0xa4a. "Troubleshooting Mailbox Moves" articles do not give any clues regarding my error:(

Can you give me the links to these cases? So is it expected bug of RU3? Something else? I can see user mailboxes I moved in Disconnected mailboxes branch.

Hi I am sorry, they are internal support cases. According to our policyI can't post them on popular forum. Question one: no offical answer. Most of engineers think it is by design. Question two: I haven't found it from bug list. Maybe it will be updated. Only one user solved it by remove whole origin database. maybe it is workround.Terence Yu TechNet Community Support

I'm seeing both of these issues as well, Exchange 2010 SP2 RU3. Same (well, except for the mailbox ID) error message on the mailbox server regarding the "failed to delete....error 0xa4a"

Hi, I am seeing the exact same issues with build numbers and the move completed with warnings; has anyone got an update on this? Any help much appreciated.

Same problem here - but running SP2 RU4. Version number is off - maybe cosmetic ? EMC detail shows - Warning: Failed to clean up the source mailbox after the move. Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) Windows application log shows - Failed to delete the mailbox of 315f2ea7-5810-407a-8227-8ab90ab6fbe1 with error 0xa4a. Are these simply softdeleted and need to be removed manually? But wouldn't a successful move have the mailbox soft deleted as well ?