The server cannot service this request right now in Office 365

Hello,

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?

Thanks,
John
LVL 1
jhiebAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
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
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vasil Michev (MVP)Commented:
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.
0
jhiebAuthor Commented:
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.
0
Vasil Michev (MVP)Commented:
Are you aiming to migrate entire mailboxes or only messages? For the first option, you can review this article:

http://help.outlook.com/en-ca/140/ms.exch.ecp.emailmigrationstatuslearnmore.aspx

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:

http://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx

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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.