Cannot Migrate From Office365 to Onpremise

I am having troubles moving mailboxes from Office 365 to my on-premise lab.  My customer is also having the same issue.  There no issues moving from on-premise to the cloud.  

Exch2013 Hybrid & Exch2007 Mailbox/CAS

When submitting the move request back on premise:

New-moverequest -identity -OutBound -RemoteTargetDatabase "CN=Mailbox Database,CN=First Storage Group,
CN=InformationStore,CN=EXCH2007,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=jbdetroit,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=jbo365,DC=net" -RemoteHostName -RemoteCredential $jbo -TargetDeliveryDomain

I get the following error:

The call to '' failed because no service was listening on the specified endpoint. Error details: There was no endpoint listening at that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. --> The remote server returned an error: (404) Not Found.
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=BY2PR07MB028,RequestId=0c980da7-6449-4c16-bd6a-34f11fce6167,TimeStamp=9/30/2013 7:59:12 PM] EAAD4B9A,Microsoft

I can see the requests hitting EWS in the logs:

2013-09-30 19:49:57 POST /EWS/mrsproxy.svc - 443 jbo365\jbigham - - 404 0 0 93
2013-09-30 19:50:03 POST /EWS/mrsproxy.svc - 443 jbo365\jbigham - - 404 0 0 78
Who is Participating?
JabtechConnect With a Mentor Author Commented:
I'm sorry, but that is not an acceptable solution.  That is a workaround.  

I found out what the issue was...

There isn't a need to provide the full distinguished name of the on-premise Exchange database.  The PowerShell command only requires the "name" of the database (Mailbox Database) and Exchange knows how to read that.

Problem solved.
This may be time-consuming...but has worked for me when I have run into issues.

1) Connect to cloud exchange from outlook
2) Export the mailbox to the local drive
3) Create a new outlook profile to connect to the local exchange and restart outlook to that profile
4) Import the mailbox from the local drive - this will put everything into the local exchange server
JabtechAuthor Commented:
I resolved the issue on my own after additional troubleshooting.
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.

All Courses

From novice to tech pro — start learning today.