Troubleshoot GAMME

Troubleshooting tools

Pre-migration diagnostics: To determine if there are issues with your configuration or users list, you can run diagnostic tests before you migrate data. The utility alerts you to errors and displays information on the Output screen. For details, see "Migrating Data" chapter in the GAMME Admin Guide (PDF).

Migration reports: After you run a migration, you can check the migration report to determine if any errors occurred, why they occurred, and which users were affected by them. For details, see the "Viewing Migration Reports" chapter in the GAMME Admin Guide (PDF).

Migration logs: You can examine log files for more information about migration errors or provide logs to Google Support. For details, see the "Troubleshooting Issues" chapter in the GAMME Admin Guide (PDF) Also, the Google Log Analyzer tool can scan your Trace log files and quickly identify many types of migration issues. Go to the analyzer and upload your log files.

Troubleshooting articles

Other help articles

Still have questions? See the GAMME Admin Guide.

Common Issues & Solutions

My migration fails immediately because the administrator's Microsoft® Exchange profile could not be created

The Microsoft® Exchange Server may not be running.

You may have a network issue that is blocking a connection between the client machine and the Microsoft® Exchange Server. Ping the server from the client machine to verify a connection.

You may have used the wrong name for the Microsoft® Exchange Server or for the administrator. Use the following method to verify the Exchange Server name and administrator user name:

On the client machine, use Control Panel > Mail to create a Microsoft Outlook® profile for the administrator account you want to use for migration. When that profile has been created, use the Microsoft® Exchange host name from that profile for the Microsoft Exchange Server parameter in Step 1, and use the user name from that profile for the Microsoft Exchange Administrator User name parameter in Step 2.
The Microsoft® Exchange Server does not recognize the administrator name I am using for the migration

Verify that you have entered the correct name and password for the administrator.

You may have used the wrong name for the Microsoft® Exchange Server or for the administrator. Use the following method to verify the server name and administrator user name:

On the client machine, use Control Panel > Mail to create a Microsoft Outlook® profile for the administrator account you want to use for migration. When that profile has been created, use the Microsoft® Exchange host name from that profile for the Microsoft Exchange Server parameter in Step 1, and use the user name from that profile for the Microsoft Exchange Administrator User name parameter in Step 2.
GAMME 0x80004005 errors when migrating from Exchange 2010

Issue:

Some users fail to migrate from Exchange 2010 with a high percentage of migration errors. In the logs, you see GAMME 80004005 errors ("Failed with 0x80004005") paired with random MAPI calls to Exchange 2010.

You see will see "BufferTooSmall" errors in the remote procedure call (RPC) Client Access log on the Exchange Server 2010 Client Access server. Example:

2012-10-15T00:04:27.367Z,165145,991,"/o=domain, Inc./ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=exchangemigrationaccount",,ExchangeMigration.exe,12.0.6606.1000,Classic,,,ncacn_ip_tcp,,0,,,RopHandler: ReadRecipients: Unable to add even one recipient to the RecipientCollector.. Error code = BufferTooSmall

Resolution:

This is a known issue with Microsoft Exchange 2010 and Outlook 2007/2010. You will need to upgrade to Exchange 2010 SP2 RU3.

For more information, see Microsoft's support article KB2674185, blog post, and wiki page.
GAMME crashes soon after starting

If the GAMME app quickly crashes after starting, make sure that you're running it on your client machine and not on the Exchange server. Running the utility on the server itself can cause it to crash. Read more about why this happens on Microsoft's support site.

If you think GAMME could be crashing because of load balancing issues, see "Prepare your Microsoft® Windows client machines" on page 27 of the GAMME admin guide.

Migration fails for a single user

Check the following:

  • That the user's name or SMTP address is formatted correctly in the user file.
  • That the user is not hidden the Global Address List.
  • Verify that the user has an account on the Microsoft® Exchange Server.
  • Verify that the user has logged in to Google Apps at least once, accepted the terms of service, and finalized creation of the account.
Migration fails due to invalid consumer secret

Copy and paste the consumer secret from your Google Apps control panel. You can find the consumer secret in the following location:
Advanced Tools tab > Authentication > Manage OAuth domain key > OAuth consumer secret

Migration fails due to OAuth error

Make sure that you complete Steps 1-3 in Migrate data from Exchange using GAMME, including Enable the Provisioning API, Enable your OAuth consumer key, and Specify the API scopes. For additional details, see 0x80041065 in GAMME Error Codes.

Issues caused by anti-virus software or a plug-in

Sometimes, additional processes running on your machine (for example: anti-virus, desktop search, or backup software) will access the migration tool's database file during the migration. This interrupts the tool's ability to save the state of that message. If you think you're affected by this issue, check for the follow error codes in your log files:

0x80040109
Fail:While stamping the message

This problem does not indicate that messages failed to migrate, only that the tool couldn't save 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 them being migrated previously. This will not cause message duplication, but it may lead to duplicate calendar events or contacts.

Migration fails due to a non-existent Google Apps user

Google Apps Migration for Microsoft® Exchange does not provision users in Google Apps. You need to create the Google Apps user accounts before you migrate data.

Migration fails for only some messages

Those messages (including attachments) may exceed the size limit imposed by Gmail, or the messages may contain attachment types that are blocked by Gmail.

Or, you may need to remove folder size limits and expose additional folders to the migration tools. See IMAP and POP access for instructions.

Migration fails with error 0x80070005

An error message similar to the following appears on the Output screen or in the Trace log:

E:Generic ExchangeMigration!SetPropertyGuid @ 641 (user@domain.com)> Failed with 0x80070005, last successful line = 637.

The most common cause is that user accounts don't have the required permissions for the utility to read users' mailboxes. To resolve this issue, ensure that you grant accounts the Receive As permission on Microsoft Exchange. If accounts have the Receive As permission and the error persists, your Exchange environment may require users' accounts to also have the Send As permission.