• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3524
  • Last Modified:

Mailbox Fails to Move using Move Mailbox in Exchange 2007

When trying to move mailboxes from Exchange 2003 to exchange 2007 utilizing "Move mailbox" feature on Exchange 2007, all mailboxes move except one. (have the proper permissions, user has deleted rules)
This is the error received in the Move Mailbox log.

[4/26/2011 6:28:25 PM] [0] [user] Mailbox was locked successfully.
[4/26/2011 6:28:25 PM] [0] [user] Moving messages.
[4/27/2011 2:28:23 AM] [0] [user] Deleting mailbox from mailbox database:
      szServer: 2007server.xxxx.xxx.xx.us
      pguidMdb: {B4A8EAE5-60E7-4962-BF59-9659C6D21A65}
      pguidMailbox: {19F733AB-BE6C-4717-9273-E20DA94971C0}
[4/27/2011 2:28:23 AM] [0] An unexpected error occurred when reporting progress: The pipeline has been stopped.
[4/27/2011 2:28:23 AM] [0] The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] [user] Mailbox '{19F733AB-BE6C-4717-9273-E20DA94971C0}' was deleted successfully.
[4/27/2011 2:28:24 AM] [0] An unexpected error occurred when reporting progress: The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] [user] Trying to unlock mailbox:
      szServer: 2003server.xxxx.xxx.xx.us
      pguidMdb: {E5C286A2-48B7-46EA-B08E-41FDC4CE79E2}
      pguidMailbox: {19F733AB-BE6C-4717-9273-E20DA94971C0}
[4/27/2011 2:28:24 AM] [0] An unexpected error occurred when reporting progress: The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] [user] Mailbox was unlocked successfully.
[4/27/2011 2:28:24 AM] [0] An unexpected error occurred when reporting progress: The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] Error was found for User Name(user@xxxxx.us) because: Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error: The operation was cancelled., error code: -1056749164
[4/27/2011 2:28:24 AM] [0] An unexpected error occurred when reporting error: The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] [user] The operation has finished.
[4/27/2011 2:28:24 AM] [0] The mailbox has been moved, but an unexpected error occurred while trying to apply policies or clean source mailbox: The pipeline has been stopped.
[4/27/2011 2:28:24 AM] [0] The pipeline has been stopped.

I find lots of info about MAPI error, but this doesn't seem to be related to MAPI.

Any help would be greatly appreciated.

Thanks...Harold
0
harold mcmullen
Asked:
harold mcmullen
  • 3
  • 2
1 Solution
 
AmitIT ArchitectCommented:
Can you export complete data to a PST. Clear all data from Outlook and then move the empty mailbox. If moved, merge PST back again.
0
 
harold mcmullennetwork techAuthor Commented:
Thanks amitkulshrestha,
 probably could, already looked at that, but it isn't addressing the cause of the error.
all of the items i found on internet with "error code: -1056749164" also have an additional explanation of MAPI problems. Mine doesn't. "while trying to apply policies or clean source mailbox" seems to be the key, but does anyone know what exactly that means.
(I have "exchange administrator" rights and have made sure that have full control over this mailbox, but also every other mailbox move has went smoothly)
0
 
AmitIT ArchitectCommented:
Below are the possible reasons.

1) Once you start the MB move an, In Transit flag is appended to the mailbox. Now the problem is that, this flag remains after mailbox move also and if you again try to move same mailbox, it won't work.

To fix this you need to goto EMC>Recipient configuration>Move Request Node>Select the mailbox>Right click and click on "Clear Move Request"

2) Insufficient Rights: Below are the 2 reasons
    a) You are part of Domain Admin group, and Domain admin is not allowed to manage Exchange server, until you gave the rights properly
     b) Blocked Inheritance: If inheritance is blocked, permission cannot be assigned to the Exchange mailbox. Check this issue also.

You can also use ADSI edit for fixing block permission issue. Open ADSIEdit.msc tool. Browse to the account properties, with which you are trying to move the mailbox. Open security tab>Advance>Click on the "Include inheritable permissions from this object’s parents">Click apply ok

Hope this helps
0
 
harold mcmullennetwork techAuthor Commented:
It seems to be related to the "corrupted tasks" the user had in his "tasks" folder. After having user remove all tasks, move went without a hitch.
amitkulshrestha, thank you for your suggestions.
0
 
harold mcmullennetwork techAuthor Commented:
i only found i google entry that mentioned "tasks' which led me to look at "tasks" as the possible culprit. as it turned out, the user had corrupted tasks and it worked afterwards.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now