Monday, January 4, 2010

Mailbox move error exchange 2010


Some of the mailboxes are failing with fallowing errors

  • Active Directory operation failed on VMDC02.YAW.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.Active directory response: 00002098: SecErr: DSID-03150E8A, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0.
  • The user has insufficient access rights.


On the user object security settings, “include inheritable permissions from this object’s parent is not checked in


Place a check mark there , and also

The account you logged into Exchange server , make sure it is a member of domain administrators and domain administrators does have full rights on the problem user object properties as shown here , if you have special security requirements you can move domain administrators full right after move complete successfully.

One last thing you need to do is to cancel , move request for this user if not you receive fallowing error


copy and paste this into word or note pad

to see the status copy and paste the CMD-Let as shows into Shell

Get-MoveRequestStatistics -MoveRequestQueue 'DB3 (Teachers)' -MailboxGuid 8eed186b-90c4-41eb-9f78-c42f7315d210 -IncludeReport | fl


Same goes for removing it

Remove-MoveRequestStatistics -MoveRequestQueue 'DB3 (Teachers)' -MailboxGuid 8eed186b-90c4-41eb-9f78-c42f7315d210 -IncludeReport


After move request has been cancelled move on and try again to move the problem mailbox

Permissions required for mailbox moves

Oz Casey , Dedeal

MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

Http:// (Blog

Http:// (Blog)

Http:// (Blog)


Usman said...

I'm currently migrating from Exchange 2003 to Exchange 2010, I have a move request that has been running for almost 10hrs, which is unusually long for only 50MB of data in the mailbox. What happens when I remove an In-Progress move request?

Oz Casey Dedeal said...

Nothing you wont hurt anyting MB wont get moved to E210
Any erros on the event logs at all?


DaveShack said...

Oz, you have a significant typo in your remove-moverequest Powershell script. It looks right in the screenshot, but not in what you can copy\paste.

mustafa said...

I hope solution following link:

Oldhaus Fibers & Rabbits said...

I'm working on migrations from Ex03 to Ex10.

I'm getting some mailbox errors (not permissions or size) but corruption errors.

What can I do about them?

12/3/2010 4:21:00 PM [lcua67] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.
<baditem errorType="MapiExceptionMaxSubmissionExceeded" errorCode="0x80004005" flags="0x00000000"

Anonymous said...


Underlying corrupted Item might be the root cause for some of these errors.

One idea to try (if not already done) is to run ISTINTEG tool against the relevant mailbox stores.

Else, you can try to:

1. create a new storage group

2. create there a mailbox store

3. perform a move mailbox for all "failing" mailboxes

Lastly, give it another Mig try.