On Demand Migration for Email Current - User Guide

Introduction Preparing Migrations Test and Pilot Migrations Configuring and Running Migrations Post Migration Glossary

Validating Connections

Validating Connections

After entering the connection properties of a source or target email service, enter the name of a source or target mailbox (and corresponding password if you selected the User end-user credentials option). Then click Test Connection. On Demand Migration for Email uses the login credentials you specified to connect to that mailbox. Depending on your type of source and target email service, different connection errors may be reported.

 

Note: You need to configure your firewalls to accept the WebRole IP addresses that ODME uses to validate connections. To obtain the current IP addresses, open the About box from the ODME home page:

Refer to the sections below for validation errors specific to your email platform:

G Suite

G Suite

On Demand Migration for Email connects to the URL http://www.google.com/a/example.com (example.com is from the Google Domain setting above). If that page exists as a Google domain, the next step is to connect to the G Suite server using the OAuth 2 protocol.

Error Description/Resolution
Any message saying an exception occurred because of an “invalid grant”, “invalid request”, or “400 bad request error”.

Each scope URL gives ODME access to a different type of data. ODME checks that each scope has been granted when validating the connection. Note: All scopes need to be added for validation to succeed, even if the options to migrate certain item types are disabled.

Make sure that the test mailbox used for validation exists. Confirm that the client name and API scopes have been set correctly in the Google Admin console. (The Connections screen shows instructions on doing this after you have signed into G Suite with a super admin account.)

Unable to connect to the Google Contacts API.

The test mailbox does not exist, the API scopes are not set correctly, or network issues are preventing ODME from reaching G Suite.

Make sure that the test mailbox used for validation exists. Confirm that the client name and API scopes have been set correctly in the Google Admin console. (The Connections screen shows instructions on doing this after you have signed into G Suite with a super admin account.)

Unable to connect to the Google Calendar API. The test mailbox does not exist, the API scopes are not set correctly, or network issues are preventing ODME from reaching GSuite. Make sure that the test mailbox used for validation exists. Confirm that the client name and API scopes have been set correctly in the Google Admin console. (The Connections screen shows instructions on doing this after you have signed into G Suite with a super admin account.)
Invalid Mailbox (Unable to retrieve folders)

The test mailbox does not exist or does not have IMAP access enabled, the API scopes are not set correctly, or network issues are preventing ODME from reaching G Suite.

Make sure that the test mailbox used for validation exists and has IMAP access enabled. Confirm that the client name and API scopes have been set correctly in the Google Admin console.

Sun ONE/iPlanet

Sun ONE/iPlanet

Error Description/Resolution
The test mailbox doesn't exist. You may see the following error when you test the connection: There was a problem testing your connection. Please try again. Verify that the mailbox name does exist in SunONE/iPlanet and that you have spelled the name correctly.
Server name is incorrect, or firewall is blocking access.

You may see the following error when you test the connection:

Failed to connect sunone.example.com IMAP server.

Check that your server name is spelled correctly and that your firewall is open to the On Demand Email Migration for Email IP addresses to port 7191. To obtain the current IP addresses, open the About box from the ODME home page:

Novell GroupWise

Novell GroupWise

Error Description/Resolution
The test mailbox doesn't exist.

You may see the following error when you test the connection:

Invalid Mailbox Name: test.mailbox Code= D101, Description= User not on post office.

Verify that the mailbox name does exist in GroupWise and that you have spelled the name correctly.

Server name is incorrect, or firewall is blocking access.

You may see the following error when you test the connection:

Cannot find server. Server:groupwise.example.com, Port:7191.

Check that your server name is spelled correctly and that your firewall is open to the On Demand Email Migration for Email IP addresses to port 7191. To obtain the current IP addresses, open the About box from the ODME home page:

Related Documents