GAMME Error Codes
Google Apps Migration for Microsoft® Exchange (GAMME) Error Codes
|Error Code||Explanation||Relevant Links|
|0x80004005||GAMME had problems calling certain MAPI commands. This issue is generally benign. If this issue is causing problems, please install the latest service packs for your Microsoft Exchange server and Windows environment. If you're still experiencing problems, see the 0x80004005 bullet in the GAMME troubleshooting article.||System Requirements|
|0x80041001||Identify the affected user in the trace file (the username will appear near the number '80041001'), then check that the specified user exists in Google Apps and is not suspended or disabled.||Restore a suspended user account|
|0x80070057||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.
|0x80040109 or Fail:While stamping the message||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.
|Some files being accessed by the migration tool were not found. Please ensure that Outlook is installed on the system and that the user list, resource files and PST files or folder paths are accessible.||System Requirements|
|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.
HTTP/1.1 401 Token invalid
|An invalid domain Consumer Secret was specified during configuration. Please double-check the specified Consumer Secret in your domain Control Panel to ensure you are using the correct key.
In some cases, we have found that this behavior can be caused by a clock synchronization issue. Please check the timezone specified on the host machine, and ensure that Microsoft Windows is synchronized to internet time servers. A few seconds of deviation is fine, but the time should not be minutes off.
|Migrate data from Exchange using GAMME|
Invalid/non-existent Google User
|At least one migrating user is either not an existing Google Apps user or cannot be accessed in Google Apps by the migration tool. Find the affected user in the logs (search for 'Invalid/non-existent Google User' or '0x80041007'), then check the following for this user:
- Verify via your control panel that the user exists in Google Apps. Ensure the domain name is correct and is not an alias.
- Ensure that the user account given is the user's primary e-mail address and not an e-mail alias
- Check that the CSV file you're using is properly formatted as detailed in the Administration Guide
- Check that your OAuth consumer key is enabled (see the Administration Guide).
- Check that all API scopes specified in the Administration Guide are explicitly enabled. Note that migrations to secondary domains require that the OAuth scopes specified must be explicitly authorized in the control panel.
|Configure Google Apps Control Panel|
|0x80041194||GAMME encountered a file that violates Google's message size restriction. This is likely caused by an attachment that's over 25MB after it's been encoded on the legacy system.|
|0x8004010f||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.
|0x80040305||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.
|0x8004011d||The Exchange administrator account used does not have sufficient permissions to open end-user mailboxes.
Occasionally, there is a problem with legacy administrator accounts. Please create a new administrator user on Exchange and give the account full mailbox access (MBA) for all end-user accounts. Then use this account for migration. You can leave the original administrator account as is and delete the migration administrator account after the migration is complete.
If migrating from PST files, ensure that the PST is not password-protected.
This error code can also occur if your Exchange Server exceeded the 32 MAPI session limit during a migration. You can resolve the issue by configuring GAMME or your Exchange Server.
|Permissions issue: Mail Server Requirements
MAPI issue: GAMME Admin Guide
|0x8004060c||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).
||The migration tool encountered a quota limit when connecting to Exchange.
Please see the Microsoft article here for instructions on resolving the issue on the Exchange server side. Once you've made the required changes, try the migration again.
|0x80070005||This is typically related to full MBA legacy admins not having the appropriate permissions. Please create a new administrator user on Exchange and give the account full mailbox access (MBA) for all end-user accounts. Then use this account for migration. You can leave the original administrator account as is and delete the migration administrator account after the migration is complete.|
|0x80042011||This error means that an IMAP folder couldn't be selected in order to migrate its messages. Generally these errors are seen whenever the folder is hidden, shared, has restricted access, or when the contents of the folder are corrupted.|
|0x80070002||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
Configure Google Apps Control Panel
|GetOutlookExePath.*Failed||It appears that the machine running the GAMME migration tool doesn't have Outlook installed. A fully up-to-date supported version is required for all Exchange and PST file migrations as Outlook includes a library for translating email messages from Microsoft's proprietary format to the MIME standard prior to the upload to Google's mail system.
To resolve this issue, please install a compatible version of Outlook as described in the administration guide for the GAMME tool on the machine running the tool, then attempt the migration again.
If the machine running the GAMME tool already has a compatible version of Outlook installed, please try uninstalling and reinstalling Outlook, ensure that you're able to open Outlook, and ensure Outlook has the latest patches.
|IMAP Error: stream error - socket could not be read or written||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.
|Permanent failure: BadAttachment
Invalid RFC 822 Message
|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.
|Viewing Migration Reports|
|0x8007065e||This issue can occur if the network timeout registry entries have been created using the wrong registry data type (for example REG_SZ instead of REG_DWORD). Use the Registry Editor (regedit), to make sure that all entries under HKEY_CURRENT_USER\Software\Google\Google Apps Migration\Other are of type REG_DWORD and not any other type.|
|0x8004106a||Communication to the server has failed. A "Server is busy. Please try again later" message is displayed.|