Here’s a dumb one. So I was running into an issue when trying to move an email from Office 365 back to my on Prem server getting this error:
The call to ‘https://webmail.domain.com/EWS/mrsproxy.svc internal-mail-servername.domain.com (18.104.22.168
caps:05FFFF)’ failed. Error details: The server was unable to process the request due to an
internal error. For more information about the error, either turn on
IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
configuration behavior) on the server in order to send the exception information back to the
client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and
inspect the server trace logs.
Well, here is what my command looked like:
New-MoveRequest "firstname.lastname@example.org" -OutBound -RemoteTargetDatabase 'servernamemsp-db-2' -RemoteHost "o365migration.edmentum.com" -TargetDeliveryDomain "edmentum.com" -RemoteCredential (Get-Credential) -Verbose
Well, the fix for this error is quite simple, if not a little dumb… Change your “remotetargetdatabase” parameter to just the name of the database you want to go to, instead of using the serverFQDNdatabasename format. The working command is below:
New-MoveRequest "email@example.com" -OutBound -RemoteTargetDatabase 'msp-db-2' -RemoteHost "o365migration.edmentum.com" -TargetDeliveryDomain "edmentum.com" -RemoteCredential (Get-Credential) -Verbose
Learning Powershell? It’s a bit spendy, but as in most things technology, with this book, you get what you pay for.