Summary: When migrating from an on-premises Exchange Server to Exchange Online using the cutover migration method, you may encounter the ‘Microsoft Exchange Data Storage Management Migration Transient Exception’ error. In this post, we’ve mentioned the ways to resolve this error. Also, you’ll find an EDB converter tool that can help you migrate to Office 365 without any hassle.
Contents
Migration from an on-premises Exchange Server to Exchange Online, i.e., Office 365 can be a bit tricky. In some situations, you may face ambiguous errors that would not have a direct point to the problem. So, finding the right solution would be quite difficult.
In this post, we will be discussing the ?Microsoft Exchange Data Storage Management Migration Transient Exception? error. This error usually occurs while migrating from an on-premises Exchange Server (2010 or newer) to Office 365 using the cutover migration method.
While trying to do a cutover migration from the local Exchange Server where Outlook Anywhere is used to Exchange Online, the migration application doesn?t create a migration endpoint and throws the following error.
Microsoft.Exchange.Data.Storage.Management.MigrationTransientException: We weren't able to connect to the remote server. Please verify that the migration endpoint settings are correct and your certificate is valid, and then try again. Consider using the Exchange Remote Connectivity Analyzer to diagnose the connectivity issues. ---> Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC server is unavailable) from cli_NspiBindHow to Fix the Error?
As a prerequisite, when migrating, always ensure that the source server or setup is healthy and everything is configured as it should be with the requirements. If you use the cutover migration method, make sure that Outlook Anywhere is set correctly and working with no issues. You should always confirm that all the services are running and functioning and that no errors are shown in the event viewer.
Since the error states ?unable to connect to the remote server?, you should check with the network team (after the analysis of router logs) that nothing is being blocked from the external-facing routers. In addition, it is also important to check the Exchange Server Windows Defender Firewall (if enabled) or any other third-party firewall. You can check the Windows firewall logs by following these steps:
- Open the Windows Defender Firewall with the Advanced Security application.
- Right-click on the root and click on Properties.
- Under the Domain Profile tab, click on Customize in the Logging area.
- In the Name field, you will find the location of the Firewall logs.
- After opening the log file, ensure that there aren?t any DROP entries. If there are any, you should try to create the necessary rules to allow the traffic.
Another thing to do is to ensure that the Exchange Server is fully updated with any Cumulative Updates needed, along with the operating system hosting the Exchange Server. If this is done and the problem persists, you need to investigate the Exchange Server configuration.
The error states an issue with the RPC Server (see the below extract).
Remote Connectivity Analyzer to diagnose the connectivity issues. ---> Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC server is unavailable) from cli_NspiBindTherefore, you need to check that Outlook Anywhere is configured correctly. To do so, follow these steps:
Step 1 ? Confirm Authentication Method
You need to make sure that the on-premises Exchange Server Outlook Anywhere client authentication method is configured as Basic Authentication. This can be set via the Exchange Management Shell (EMS) by using the PowerShell command as given below.
Set-OutlookAnywhere -Identity "<server name>\rpc (Default Web Site)" -IISAuthenticationMethods Basic,NTLM
Step 2 ? Confirm that the RPC Proxy is Working
You need to ensure that the RPC Proxy service can communicate with Outlook Anywhere and the local Domain Controllers are listening on port 6004.
Step 3 ? Verify Connectivity to the Local Server
Although Outlook Anywhere is configured, you need to make sure that it is reachable. You can do this by using Exchange Online PowerShell. You can use Office 365 to test the connectivity to the local server by running the following commands:
$pscred=Get-CredentialEnter the credentials of the global admin.
Test-MigrationServerAvailability -Credentials $pscred -ExchangeOutlookAnywhere -ExchangeServer <Internal FQDN of the Exchange server> -RPCProxyServer <FQDN of the proxyserver> -Authentication Basic -EmailAddress <AdminEmail>Here, you need to specify the internal FQDN of the Exchange Server which is the Exchange Server (for example mail.domain.com), and the RPCProxyServer which could be the same as mail.domain.com. You also need to specify the administrator email, for example, administrator@domain.com.
This command will ensure that your local Exchange Server is reachable from the Exchange Online and Outlook Anywhere (RPC over HTTP) is working fine. If the test was successful after the changes in Step 1, you can go ahead and create a migration endpoint in Office 365.
Wrapping Up
If the problem persists, it is suggested to use a third-party application, such as Stellar Converter for EDB. This application can open multiple EDB files of any Exchange Server version without the need for an Exchange Server. The application can easily browse through the EDB file and granularly export mailboxes and Public Folders to PST and other file formats. Stellar Converter for EDB can be used as a migration tool as it can export directly to another live Exchange Server mailbox database and Office 365 tenant.
