The server cannot service this request right now in Office 365

Posted on 2013-10-18
Medium Priority
Last Modified: 2013-10-27

I am migrating messages into Office 365 using Exchange Web Services and I am getting an error from office 365 stating, "The server cannot service this request right now. " 

I assume my Office 365 email server is overloaded because of too much traffic. Is there something I can do in PowerShell to make my Office 365 email server behave differently so that it can handle the amount of traffic it is receiving? I Googled this error and found possible fixes for a LAN based Exchange server. So, if I somehow establish a PowerShell connection to the Office 365 email server then I can make changes.

Has anyone encountered this error when migrating or transferring email data to their Office 365 accounts? If so, how did you get around it?

Question by:jhieb
  • 2
LVL 52

Accepted Solution

Manpreet SIngh Khatra earned 1000 total points
ID: 39584396
Hope your network bandwidth is good compared to the data your trying to Migrate.
Try with another account and whats the current Mailbox size compared to what Quota is on the Target

- Rancy
LVL 46

Assisted Solution

by:Vasil Michev (MVP)
Vasil Michev (MVP) earned 1000 total points
ID: 39584629
There are some throttling limits and you are most likely hitting them. No way for you to change them.

Why use EWS? There are plenty other ways to migrate.

Author Comment

ID: 39584718
Thanks. What other ways are you suggesting? IMAP it MAPI? I would like to use MAPI but I am challenged how to use RPC over HTTP.
LVL 46

Expert Comment

by:Vasil Michev (MVP)
ID: 39584751
Are you aiming to migrate entire mailboxes or only messages? For the first option, you can review this article:


For individual messages, best use .pst files and import directly to Outlook. Alternatively, you can use the PST Capture tool to automate this if you have many mailboxes/psts:


If you are migrating from non-exchange environment you can use IMAP migration, it also allows you to exclude certain folders.

If none of these methods is suitable solution for you, you will just have to tone down the number of requests. As mentioned previously, there is no way for you to control throttling settings in Exchange Online. We cannot even view them to tell you the exact limit, but the default setting for EwsMaxConcurrency in Exchange 2013 is 10. PowerShell is also limited to 3 sessions per user.

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Let us take a look at the scenario, you have a database that is corrupt and you run the ESEUTIL command only to find you are unable to repair it. How do you now get the data back?
If there is anything erroneous with Exchange Database, it causes a significant effect on email communication till the user remounts the database. Further, database crash directly affects Outlook users due to which they are unable to access their ema…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Watch the video to know how one can repair corrupt Exchange OST file effortlessly and convert OST emails to MS Outlook PST file format by using Kernel for OST to PST converter tool. It can convert OST to MSG, MBOX, EML to access them. It can migrate…

624 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