Exchange Mailbox Migration errors

Posted on 2014-02-26
Medium Priority
Last Modified: 2014-03-25
I am migration 44 mailboxes to Office365. I'm using a tool called migration-wiz.

So I had to give my admin account and give myself full permissions so this tool can gain access to the mailboxes and migrate the data.

After adding myself with those full access permissions to some users everything was good. But after a while I started to get a warning upon completion which i attached the photo below.

Now I checked my event log and I see this error

"Process w3wp.exe () (PID=4260). User 'Sid~ABC\john~EWS~false' has gone over budget '326' times for component 'EWS' within a one minute period. Info: 'Policy:DefaultThrottlingPolicy_8bbb676e-a705-4b0f-a58b-30777c69d87b, Parts:CAS:325;'. Threshold value: '100'."
Question by:IT_Fanatic
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
LVL 42

Accepted Solution

Adam Brown earned 1000 total points
ID: 39890345
Yeah. There's a feature you can enable called impersonation. What's happening is you are exceeding the Office 365 throttling policy limit for number of connections to the service. Impersonation will allow you to impersonate the mailbox you're migrating to and deal with the throttling limits of each user's mailbox instead of just yours. Connect to the Office 365 Exchange remote powershell and run this:

new-managementroleassignment -role "applicationimpersonation" -user youradminemail@company.com

That will set up your admin account in O365 to run in impersonation mode, which should fix that error for you.

Author Comment

ID: 39890372
im on my computer. Where is the power shell for office 365?

The script would be this?

new-managementroleassignment -role "applicationimpersonation" -user john@abc.com
LVL 74

Assisted Solution

by:Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy earned 1000 total points
ID: 39891488
An overview of why this is happening is here:
and a bit more on the MigrationWiz blog here:

You cannot change the Throttling Policy on Office 365, as acbrown2010 described above.

Unfortunately, you must just tough it out and wait for the batches to go through -- which they eventually will.  

Try migrating mailboxes in smaller batches -- or migrate very large mailboxes (over 20GB) by themselves as a single-mailbox batch.

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 39891491
Also... if you are going to be the administrator for your Office365 service, you need to learn how to use it's powershell.

This blog post will help you do that:

Author Comment

ID: 39891600
Wait so your telling me I have to stick to the 2 at a time out of 44 mailboxes? This will take about a year to complete
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 39891684
Actually... I just took a look and see that the recommendation by acbrown2010 is somewhat correct.

MigrationWiz will actually do that change for you if you modify the Advanced Options of the connector:


(I haven't used MigrationWiz in over a year because I've found that the built-in migration tools have been working well)
LVL 42

Expert Comment

by:Adam Brown
ID: 39940949
Well, Migwiz won't set the permissions for you. You have to do that manually. You also have to set Migwiz to use that feature for it to do so.

Assisted Solution

IT_Fanatic earned 0 total points
ID: 39943258
I set the permissions. I called microsoft and they said theres just to many mailboxes and they are also very large. So the server will only migrate a few to control the  Throttling

Author Closing Comment

ID: 39952691
I also selected my comment because I contacted Microsoft and they verified the issue.

Featured Post

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.

Question has a verified solution.

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

Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…
Suggested Courses

801 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