Troubleshooting Exchange server connection

Errors may encounter during migration even with the right approach. These may be due to insufficient permissions, invalid credentials, throttling issues etc. The solution for all these hiccups is of high priority.

1. Source or Target Connection Failed to Respond

   Reason to failure:
   

   The source or target server did not respond for an extended period of time and does not return a folder set. This error message usually indicates a timeout error.

   • This error occurs due to a large mailbox, or a large folder associated with a user's mailbox.
   • The source or target server is too slow to respond due to large items count.
   • The server cannot access the mailbox due to intermittent network connection.

   Solution:
   

   Ensure that the server is up and running. Retry the migration with EdbMails Exchange or Office 365 migration software. The application migrates the data incrementally without any issues.

2. The Server Cannot Service This Request Right Now

   Reason to failure:
   

   The Exchange Web Service (EWS) failed to access the mailboxes due to throttling limits imposed by Exchange.

   • This error occurs due to a large mailbox, or a large folder associated with a user's mailbox.
   • The source or target server is too slow to respond due to large items count.
   • The server cannot access the mailbox due to intermittent network connection.

   Solution:
   

   Verify, whether the error originated on the source or target server

   • If you perform migration to or from Exchange 2010 or later, you can disable the throttling policy within the system.
   • If you perform migration to or from Office 365, enable impersonation to minimize the throttling. You can migrate to the target by using a global admin account.
   • You can also contact Microsoft support to have the throttling disabled.

3. The Remote Server Returned an Error: (404) Not Found

   Reason to failure:
   

   • The server failed to locate a file or resource.
   • The server is unable to connect to EWS within the environment and migrate the data to the target.

   Solution:
   

   • Use the appropriate URL to connect to EWS
   • The default URL for EWS is usually in the format https://mail.domain.com/EWS/Exchange.asmx
   • Perform this action from a non-domain joined computer having internet access.
   • When prompted, enter the appropriate credentials and you should see an XML document (WSDL)
   • If you have not correctly authenticated the Outlook Web App form, disable it and retry the operation.
   • Check that the IIS settings are correct. To correct the error, restart the process, return to the UI, and check the credentials again.

4. SMTP address has no mailbox associated with it

   You may receive the error message during mailbox migrations to Office 365. EdbMails attempts to log in to the target server but cannot find the mailbox to which you want to migrate the data. This error prevents you from viewing the mailbox associated with the SMTP address you enter in EdbMails.

   • If you have not previously assigned a license in the admin portal, there will be no mailbox associated with that SMTP address.
   • EdbMails cannot migrate the data to the target mailbox that has not been provisioned.

   Solution:
   

   Sign in to the Office 365 admin portal and assign a suitable license to the user having the issue; After you assign the license, wait for the changes to take effect.

5. Unable to Connect to the Remote Server

   A firewall blocks an external traffic that includes a connection from EdbMails.
   The Outlook Web Application (OWA) fails to load in time.

   Solution:
   

   If EdbMails application login fails, verify and allow the EdbMails IP, Port, and executable files in your Firewall. Click the following link to configure the Firewall settings. Check the network for overutilization. You could be migrating too many mailboxes over the network that require more bandwidth. To correct this error, migrate in smaller batches.

6. This Account Lacks Permissions to Impersonate Requested User

   EdbMails fails to impersonate the user due to insufficient permissions on the Admin account.
   This error message appears when you try to impersonate the requested user with a global admin account during Office 365 migration. EdbMails automatically configures the impersonation rights. However, it may fail in some cases.

   Solution:
   

   Refer to the following link to set the impersonation rights for Office 365 using PowerShell commands / Office 365 GUI.

7. 401 Unauthorized

   This error can occur if:

   • Your Office 365 account is locked or the password has expired
   • You enter invalid Admin account credentials in EdbMails
   • The administrator account has insufficient permissions for migration

   Solution:
   

   • Sign in to the Office 365 admin portal and unlock your account
   • Set a new password for your account
   • Reconnect to Office 365 with the admin account credentials by using EdbMails
   • Reset the proper permissions for the global admin account

   In case Multi factor authentication (MFA) is enabled in Office 365, see the following links to enable MFA and disable security defaults in Office 365.

   • Steps to Enable MFA and enforce access from other applications
   • Steps to disable Security Defaults in Office 365

8. A Specified Object was not found in the store

   This error message occurs during Exchange migration, when EdbMails is unable to open the user's mailbox to migrate data. It may be due to a permission error over "full access" rights for the admin account.

   Solution:
   

   • Verify the permissions for the administrator account
   • Ensure that the mailbox is not hidden from the global address list
   • Ensure that the mailbox is not having a folder name with a backslash character. Replace the backslash with the dash character and perform re-migration.
   • If you are still facing the issue, contact EdbMails Technical support