So you are trying to move a mailbox from Exchange Online back to your on premises Exchange Server and received the following error:
Error: MigrationTransientException: The call to 'https://hybridserver.company.com/EWS/mrsproxy.svc wstcorpcas01.wilson.com (14.3.227.0 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
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.. --> The call to 'https://remotewest.wilsongroupau.com/EWS/mrsproxy.svc wstcorpcas01.wilson.com (14.3.227.0 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 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.. --> 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 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.
Looks horrifying right? You have probably tried to use different credentials, created another Migration Endpoint object in Exchange Online, all without avail?
Also you would be scratching your head because you were able to move mailboxes to Exchange Online using the same MRSProxy without issues,
This is probably due to the fact that you have entered the database name wrong:
You probably have databases in a DAG, and when you copied the database name, it ended up something like "database name\server name".
The fact that database names are unique in an Exchange organisation, there is no need to specify the server name.
So what you need to do is enter "database name" into the Target Database field and your migration should be fine.
1 comment:
We have successfully migrated mailboxes in the same batch, however some particular users are failing. So database name is not an issue, anyway I have specified the database name only.
Kindly help if there is any other solution you may be aware of.
Thanks in advance!
Post a Comment