Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Issue moving mailboxes from one database to another in Exchange 2007

Posted on 2011-10-02
Medium Priority
Last Modified: 2012-05-12
Hi All,

I have set up an additional Exchange 2007 server onto my Domain and need to migrate all of the existing users around 15 over to the new Exchange database. I have used the 'move' option within the mailbox settings but am getting an error as follows:

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:46:54


Error was found for <mailbox> (mailbox@mailbox.co.uk) because: Error occurred in the step: Moving messages. Unable to unlock mailbox with error:
MAPI or an unspecified service provider.
ID no: 00000000-0000-00000000, error code: -1056749254

Exchange Management Shell command attempted:
'<Domain>/<Container>/<Mailbox' | move-mailbox -BadItemLimit '100' -TargetDatabase '<ServerName>\First Storage Group\Mailbox Database' -GlobalCatalog '<ServerName>' -DomainController '<ServerName>'

I am logged on as a Domain Admin, the Domain admin has full access rights, the user I am trying to move has 'allow inherit...' set in security, I have the old Exchange box sat next to the New Exchange Box on the same switch. I have ensure that there are NO limits on the target mailbox store. I have been able to move some users but when I try to move others I get this error. Also I had this error on one user then tried it again and it worked so this looks to be a networking issue to me. I have also tried moving two seperate users with two seperate move wizards running and they both fail at exactly the same time which is why I am guessing it is a network issue.

I have read through various blogs and one in particular suggested to 'dump' as the transfer takes place but no description on how to do this let alone what it actually means.

I have been working on this now for 3 days solid and really need to get a solution.  The worst case scenarion is that I export the users PSTs then move the mailbox configuration settings only to the new server. The problem with this is that I am paranoid about losing emails for my customer. If I go down this route and no-one can help with the original problem can someone give me some guidance on best practice on doing this.

Sorry it is so long a question but I needed to get all the details in...

Thanks in advance


Question by:rob1210
LVL 15

Expert Comment

by:Jaroslav Mraz
ID: 36899644
Hmm basic question and problem have you got same updates on both sides? have you had full udated servers?

Author Comment

ID: 36899674
OK let me explain in more detail about the servers.

Server 1 = Old Database Server = W2K3
Server 2 = New Database Server = W2K8 R2

Forest Functional Level = Windows 2003
Domain Functional Level = Windows 2000

The main issue here is that I am experiancing random issues as explained before but I am getting degrees of success which says to me that there is no problem with Domain and or Servers and surely must be something to do with network traffic etc...

One other additional bit of info is that all of the 15 PCs are currently switched on and I assume that they are broadcasting, could this simply be a point that at broadcasting time the network is swamped with traffic?
LVL 15

Expert Comment

by:Jaroslav Mraz
ID: 36899741
yes problems becouse of network trafic is posible.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

LVL 12

Expert Comment

by:Deepu Chowdary
ID: 36901162
Is ths happening for a single mailbox or for all mailboxes.
If it is for all mailboxes then it may be a database corruption.
If it for a single user, it may be a network issue.

--> 1.Check the latest Updates for NIC drivers.
--> 2. Use exmerge and migrate that mailbox then export mailbox and move it with -configurationonly option and in the end import the mail.
--> If those steps didnt actually work then all you can do is to run eseutil /g (corruption check) - Or "Isinteg -S Servername -Fix - Test All tests.
Hope this will work..

Expert Comment

by:Swapnil Prajapati
ID: 36901775
Run this command before you run the import-mailbox command for each user.  

 Add-mailboxpermission -identity <mailbox you are importing to> -accessrights fullaccess -user <who you are logged in as when running the exchange managment shell>

Author Comment

ID: 36902366
Hi swap,

I have, using the Exchange Management Console, set the full permission using the full permissions option, is this not the same or does the command line interface work differently? Bearing in mind I have not had to do this with the users mailboxes that have transferred succesfully.

Expert Comment

ID: 36904226
Some solutions:
[1] Have you run the ISINTEG utility against the mailbox store to determine whether any problems exist in the database?
[2] Try moving the mailbox to the same server but a different mailstore. see if that works. Then try moving to the new server.

Accepted Solution

rob1210 earned 0 total points
ID: 36906536
Hey all,

Many thanks for your advice but I have resolved this issue myself. We had the two servers connected via a switch that was chattering away causing increase in traffic. I changed the switch and all seems to be ok now with all users being migrated as we speak.

Many thanks again for the quick advice.


Author Closing Comment

ID: 36935303
Closing this accepting my comment owing to resolving this issue myself

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You finally migrated Public Folders to Office 365, decommissioned the Public Folder mailbox database and since then, when you send an email from on-premise to mail-enabled Public Folders, you get the following error: "Misconfigured public folder mai…
Last month Marc Laliberte, WatchGuard’s Senior Threat Analyst, contributed reviewed the three major email authentication anti-phishing technology standards: SPF, DKIM, and DMARC. Learn more in part 2 of the series originally posted in Cyber Defense …
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month14 days, 17 hours left to enroll

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question