This error can safely be ignored, as the tool will continue to migrate the objects without the missing field. On some of the events we're moving we are unable to locate a property in the object that we are trying to import.  A potential cause of this is an older version of Exchange or Outlook that doesn't use all of the latest fields. 

If you are seeing problems, try to create a new admin account in Exchange. If your already created a new admin, and using a profile to do the migration, make sure Cached Exchange mode is disabled and that you clicked "Always allow" on any autodiscovery messageboxes if they pop up. 

This problem does not indicate that messages failed to migrate, only that the tool couldn't save the fact that they were migrated. The only negative consequence is that if the migration is re-run at a later time with 'Only New Data' checked, the tool will attempt to migrate these messages again since it doesn't have a record of their being migrated previously. This will not cause message duplication, but may lead to calendar or contacts duplicates.

Another process (such as anti-virus, desktop search, or backup software) is accessing the migration tool's database file during the migration. This interrupts the tool's ability to save the state of that message. We recommend finding and disabling the software causing this issue for the duration of your migration.

0x80070003

ERROR_PATH_NOT_FOUND

0x80072ee2

0x80072ee7

0x80072efd

0x80072efe

0x80072ee0

0x80072f94

0x80040115

The migration tool encountered network timeouts while attempting to upload messages to Google servers. This may occur because the network was inaccessible or due to a slow network connection. Retrying the migration after some time or during during off-peak network hours may resolve this behavior. If not, set the registry keys below to extend network timeouts on the host machine.

Please add or change the following values:

- HKEY_CURRENT_USER\Software\Google\Google Apps Migration\Other\ResolveTimeoutSeconds > DWORD Value = 00000030
- HKEY_CURRENT_USER\Software\Google\Google Apps Migration\Other\ConnectTimeoutSeconds > DWORD Value = 00000030
- HKEY_CURRENT_USER\Software\Google\Google Apps Migration\Other\SendTimeoutSeconds > DWORD Value = 00000600
- HKEY_CURRENT_USER\Software\Google\Google Apps Migration\Other\ReceiveTimeoutSeconds > DWORD Value = 00000600

Note that the values above are in seconds, and may be adjusted to accommodate your network connection.

If not a network issue, may be related to autodiscovery issues with Exchange. Create an admin profile in Outlook, tick "always allow" on any autodiscovery messageboxes if they appear, and try to open the mailboxes with this profile. If it succeeds, use this profile to migrate instead of entering the server name and user credentials.

Invalid/non-existent Google User

0x80041007

Configure CSV File

This issue can occur when the user conducting the migration has insufficient privileges to access the PST, or when the tool is otherwise unable to find or access the PST file. Note that the Google Apps Migration for Microsoft® Exchange tool requires both read and write access to the PST.

If this happens for a root folder in the mailbox in an Exchange migration, then it's usually a permission related issue and you should check whether the specified admin user has full access on the end-user mailbox. In a few cases, we observed that the legacy user had some problems and recommended creation of a new admin user, grant them full MBA on all the end-users, migrate and then remove that admin user. 

1. This is caused by maximum number of open objects (folders) that an Exchange server can allow within a session. All the users are processed under the same session so all the open folders for all the users can add up.

2. The number of open folders for a user depends upon the maximum number of children folders under a parent folder. So if we have a folder tree where in we have max 10 children under a parent then we would not hit this limit even if user has thousands of folders in total, but if user has 500 folders under 1 single folder then we will hit it. It really depends upon the folder distribution.

3. Doing PST migration will really help for such user. Because open folders will not consume Exchange resources and will not count towards the limit and also we can choose to do a partial PST export.

To resolve the issue without having to change the folder structure, please try migrating the user with the GAMME PST option. Alternatively, follow the steps outlined here to increase the number of default value for the number of open objects that are allowed.

The migration tool attempted to update a message in Google Apps but failed. Typically, this occurs when the system is trying to migrate mail that has already been migrated.

This error is not fatal, as the mail has already been migrated and this error just indicates that it has already been moved. If you decide to run against the same user again, the impact of this is that bandwidth will be wasted as we try to reimport existing messages (which we will not allow).

Migration has failed because some files could not be found by the migration tool. This typically indicates one of the following problems:

- The source server could not be found - please check the server settings and authentication details (if applicable).
- The usernames specified do not exist - please double-check the source CSV file.
- Microsoft Outlook is not installed, or is an unsupported version. Note that Outlook is not needed if performing migration from an IMAP server.

Configure CSV File

This usually is related to timeout and connection issues.  GAMME retries the migration up to 10 times before it halts.

The way to resolve this is to reduce the batches of migrations you are running at one time, increase the speed of your network or increase the connection to external networks.

These errors should not halt the migration but may exist in the logs if certain messages fail as they do not adhere to the requirements for Google Apps Mail.

Please note the 'Show Reports' tool of Google Apps Migration for Microsoft® Exchange will provide a full report of messages that did not migrate.