Troubleshooting problems with unavailable Exchange Web Services

Problem:

While using CodeTwo software, your migration or backup job fails with the following error message:

Exchange Web Services are not currently available for this request because none of the Client Access Servers in the destination site could process the request.

Solution:

This error occurs when connecting to Exchange Web Services. It may be caused by incorrect configuration of the source server connection in your CodeTwo software or very strict throttling policy limits set on the source Exchange server. Follow the links below for information on how to troubleshoot this error:

Reconfiguring a source server connection in CodeTwo migration software

The error may appear during the initial migration or after using the Rescan option in the program. To fix it, try reconfiguring the source server connection that causes the error. However, make sure to use:

  • a newly created user account, as it is possible that the currently used admin account is associated with the custom throttling policy that causes the EWS-related error to occur;
  • the internal EWS URL.

To apply these settings and reconfigure the source server connection, make sure the migration job is stopped and then follow the steps below:

  1. Create a new user account in your source environment. The newly created user account will be assigned the default throttling policy. Just make sure this account meets the requirements described in this article.
  2. On the Dashboard tab of your CodeTwo migration software, click the settings (Exchange Migration settings button temp) button on the Defined source server connections card (Fig. 1.).

    797-1
    Fig. 1. Accessing source server connections configured in CodeTwo migration software.

  3. Select the source server connection used in your migration job and click Edit. This will open the source server connection wizard.

Info

If you are editing a connection to Office 365, skip directly to step 5.

  1. In the Server connection step of the wizard, select the second option: Connect to a specific server. Next, provide the fully qualified domain name (FQDN) of your server. Make sure the EWS URL field (Fig. 2.) shows the internal URL (if you are not sure, read this article to learn how to check the EWS URL).

    797-2
    Fig. 2. Configuring the source connection manually.

    Important

    Normally, using the Autodiscover Exchange Server option should also return the internal EWS URL; however, to exclude the possibility that an incorrect URL is returned, for the purpose of this article we recommend using the Connect to a specific server option instead.

  2. In the next step, Admin account, provide the credentials of the newly created user account (Fig. 3.).

    797-3
    Fig. 3. Providing the credentials of a new account that will be used to connect to the source server.

    This account needs to be assigned appropriate management roles to be able to connect to the source server and perform the migration. If you didn’t assign them yet, you can do so now, manually, or let the program assign them for you in the next step of the wizard (keep in mind that you will be asked by the program to enter the credentials of an admin who belongs to the Organization Management role group in order to assign the missing management roles).
  3. Finish the wizard. Make sure to click OK (Fig. 4.) once you’re back in the Manage source servers connections window to save your changes.

    797-4
    Fig. 4. Applying changes to the source server connection.

You can now go to the Jobs tab and try to restart the migration job or use the Rescan option. If you still encounter the same error, try changing the throttling policy for the admin account used in your CodeTwo software. Read more

Reconfiguring a server connection in CodeTwo Backup

The EWS-related error may appear while running an Exchange backup job. To fix it, try reconfiguring the server connection that causes the error. However, make sure to use:

  • a newly created user account, as it is possible that the currently used admin account is associated with the custom throttling policy that causes the EWS-related error to occur;
  • the internal EWS URL.

To apply these settings and reconfigure the server connection, make sure the backup job is stopped and then follow the steps below:

  1. Create a new user account in the environment you are backing up. The newly created user account will be assigned the default throttling policy. Just make sure this account meets the requirements described in this article.
  2. On the Dashboard tab of CodeTwo Backup, click the settings (Exchange Migration settings button temp) button on the Defined server connections card (Fig. 5.).

    797-5
    Fig. 5. Accessing server connections configured in CodeTwo Backup.

  3. Select the server connection used in your Exchange backup job and click Edit. This will open the Exchange Server connection wizard.

Info

If you are editing a connection to Office 365, skip directly to step 4.

  1. In the Server connection step of the wizard, select the second option: Configure connection manually. Next, provide the fully qualified domain name (FQDN) of your server. Make sure the EWS URL field (Fig. 6.) shows the internal URL (if you are not sure, read this article to learn how to check the EWS URL).

    797-6
    Fig. 6. Configuring the server connection manually.

    Important

    Normally, using the Autodiscover Exchange Server option should also return the internal EWS URL; however, to exclude the possibility that an incorrect URL is returned, for the purpose of this article we recommend using the Configure connection manually option instead.

  2. In the next step, Admin's credentials, provide the credentials of the newly created user account (Fig. 7.).

    797-7
    Fig. 7. Providing the credentials of a new account that will be used to connect to your server.

  3. Finish the wizard. Make sure to click OK (Fig. 8.) once you’re back in the Manage server connections window to save your changes.

    797-8
    Fig. 8. Applying changes to the server connection.

You can now go to the Jobs tab and try to restart the backup job. If you still encounter the same error, try changing the throttling policy for the admin account used in your CodeTwo software. Learn more

Changing the throttling policy settings on the source server

Important

It is not possible to modify throttling policies on your own in Exchange Online (Office 365). Therefore, this section applies only to on-premises Exchange servers.

An Exchange throttling policy can significantly affect migration or backup processes (learn more). If you have configured a more rigorous throttling policy in your source environment, you should try assigning this environment's default throttling policy settings to the admin account used in your CodeTwo software to connect to that environment.

For safety reasons, it is recommended to create a new throttling policy that will inherit all settings from the default throttling policy (Global Throttling Policy). The newly created policy can be then assigned to the admin account mentioned above. To do so, follow these steps:

  1. Open the Exchange Management Shell or connect to your source server remotely using the PowerShell console (see this article for more information).
  2. Create a new throttling policy by running the following cmdlet:
    New-ThrottlingPolicy <name>
    
    where <name> is the name of the policy, e.g. DefaultPolicy.
  3. Assign this policy (e.g. DefaultPolicy) to the admin account used in your CodeTwo software by executing the cmdlet below:
    Set-Mailbox "<mailbox name>" -ThrottlingPolicy DefaultPolicy
    
    where <mailbox name> is the name or alias of the mailbox account, e.g. administrator@company.com.

When you're done, you can try running the migration or backup job in your CodeTwo software straight away.

Important

If assigning the default throttling policy setting didn’t fix the problem or if you made changes to the default policy in the past, you should consider creating a new custom throttling policy with higher limits than the default ones or with unlimited access to the server. Refer to this article to learn how to do so.

See also: