Duet AI is now Gemini for Google Workspace. Learn more

Understand GWMME error codes

You might encounter the following error messages and codes when using Google Workspace Migration for Microsoft Exchange (GWMME).

Try the Log Analyzer

This tool can identify most issues within a few moments of submission. 

Error codes

Error code & message Explanation & troubleshooting
0x80004005 This issue is generally benign. However, if it's causing problems, install the latest service packs for your Microsoft Exchange server and Windows environment. For details, see GWMME system requirements.

If you're still experiencing problems, see GWMME 0x80004005 errors.


Fail:While stamping the message

This error doesn't indicate a message failed to migrate—it just means GWMME didn't retain a record of the message migration.

The only negative consequence is if the migration is re-run at a later time for only new data, the tool will attempt to migrate the message again because it doesn’t have a record of it. This might lead to duplicate calendar events and contacts.

The cause of the issue is another process (such as anti-virus, desktop search, or backup software) is accessing GWMME's database file during the migration. The tool isn’t able to save a record of the message. Find and disable the software causing the issue for the duration of your migration.

0x8004010f This issue can occur when the user conducting the migration has insufficient privileges to access the PST file or when GWMME is unable to find or access the PST file. GWMME requires both read and write access to the PST file.

If this happens for a root folder in the mailbox in an Exchange migration, then it's usually a permission-related issue. You should check whether the administrator has full access on the end-user mailbox. You can also create a new administrator user in Exchange and give the account full mailbox access for all end-user accounts. Then, use the new account for the migration. You can delete the new administrator account after the migration is complete.









GWMME encountered network timeouts while attempting to connect or upload messages to Google servers. This can occur if the network is inaccessible or if there’s a slow network connection. Retrying the migration later or during off-peak network hours might resolve the issue.

Note: Seeing this error in the logs is not a cause for concern. However, user or admin intervention is needed if the error prevents some messages from migrating.

If retrying the migration is not successful, set the following registry keys to extend network timeouts on the host machine:

  • 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: The values are in seconds and can be adjusted to accommodate your network connection.

If this doesn't resolve the issue, the error might relate to autodiscovery issues with Exchange. Create an administrator profile in Microsoft Outlook and check any always allow autodiscovery message boxes. Then, try to open the mailboxes with the new profile. If that’s successful, use this profile to conduct the migration instead of entering the server name and user credentials.

0x8004011d The Exchange administrator account doesn't have sufficient permissions to open user mailboxes. For details, see GWMME system requirements.

Occasionally, there’s a problem with legacy administrator accounts. Create a new administrator user on Exchange and give the account full mailbox access for all user accounts. Then, use the new account for the migration. You can delete the new administrator account after the migration is complete.

If you’re using PST files for the migration, ensure the files aren't password protected.

The error code can also occur if your Exchange server exceeds the MAPI session limit during a migration. You can resolve the issue by adding configurations to GWMME or your Exchange server. For details, see the GWMME Admin Guide.

0x80040154 The most common cause of this error is an incompatible version of Outlook. Try running GWMME on a machine using an older version of Outlook, such as Outlook 2010 (32-bit version).
0x80040305 This is caused by exceeding the maximum number of open objects (folders) an Exchange server can allow within a session. All the users are processed under the same session, so all open folders for all users can add up.

The number of open folders for a user depends on the number of child folders under a parent folder. For example, a folder tree with 10 children under a parent wouldn't hit the limit. However, a folder tree with 500 folders under a single folder would hit the limit.

To resolve the issue without having to change the folder structure, try migrating the user with a PST file.

0x8004060c GWMME attempted to update a message in Google Workspace but failed. Typically, this occurs when the system is trying to migrate mail that’s already migrated but was moved post-migration.

This error is not fatal as the mail is already migrated.

0x80040900 GWMME encountered a quota limit when connecting to Exchange.

Consult your Microsoft documentation for more information on how to configure named properties and replica identifier quotas.

After you make any required changes, try the migration again.

0x80041001 A user is not valid.

Identify the user in the trace file (the username is near the number 80041001). Then, check if the specified user exists in Google Workspace and isn't suspended or disabled. If needed, see Restore a suspended user.


Invalid/non-existent Google User

At least one migrating user doesn't exist in your Google Workspace account or can't be accessed in Google Workspace by GWMME. Find the affected user in the logs by searching for "Invalid/non-existent Google User" or "0x80041007." Then check the following for the user:
  • Verify in the Google Admin console the user exists in Google Workspace. Ensure the domain name is correct and isn’t an alias.
  • Ensure the user account has the user's primary email address and not an email alias.
  • Make sure the CSV file you're using is properly formatted. For details, see Create CSV files for your migration.
  • Verify your OAuth consumer key is enabled.
  • Ensure all API scopes specified in Authorize GWMME for your account are enabled.


This error can be caused by clock synchronization. Check the time zone specified on the host machine and ensure Windows is synchronized to internet time servers.
0x80041066 A message has been skipped because it exceeds the Gmail message size limit. For details about message limits, go to Send attachments with your Gmail message.

If you want to move the message to your new account, you must do so manually (for example, by adding as a file to Google Drive).

0x8004106a Communication to the server failed. You get a "Server is busy. Please try again later" message.

Try running the migration again.

0x8004106c The MAPI message could not be translated to MIME format.

Ensure your version of Outlook contains the latest patches for that version. If this doesn't resolve the issue, upgrade to a newer version of Outlook.


Failed to upload calendar event

If you get this error with a Found calendar address notification in the logs, you might be trying to migrate the same calendar data to a different user and the source user has secondary calendars. GWMME attempts to migrate the data to the same calendar, but the target user doesn't have access to the calendar, causing 404 errors from the API.

To resolve this issue:

  1. Open a command prompt.
  2. To clear the IDs of secondary calendars, enter the following command:


    For details, go to Migrate data using the command line.

  3. Remigrate the calendars.

    For details, go to Migrate content again.

0x80041194 GWMME encountered a file that violates Google's message size restriction. This is likely caused by an attachment that's over 25 MB after it's encoded on the legacy system.
0x80042008 There are incorrect IMAP connection settings.

Check the IMAP connection security settings as the connection between GWMME and the IMAP server could not be established.

0x80042011 An IMAP folder couldn't be selected in order to migrate its messages. Generally, this error occurs if the folder is hidden, shared, or has restricted access, or if its contents are corrupted.
0x80070002 Migration failed because some files couldn't be found by GWMME. This is usually because:
  • The source server couldn't be found. Check the server settings and authentication details.
  • The usernames specified don't exist. Recheck the source CSV file.
  • Outlook isn't installed or is an unsupported version. (Outlook isn't needed if you're migrating from an IMAP server.) For details, see GWMME system requirements.


Some files that need to be accessed by GWMME weren't found.

Ensure Outlook is installed on the system (see GWMME system requirements) and that the user list, resource files, and PST files or folder paths are accessible.

0x80070005 This error is typically related to the legacy administrator not having the required permissions. Create a new administrator user on Exchange and give the account full mailbox access for all user accounts. Then, use the new account for the migration. You can delete the new administrator account after the migration is complete.
0x80070057 This error can safely be ignored because GWMME continues to migrate the objects without the missing field.

If you're experiencing problems, try to create a new administrator account in Exchange. If you already did this and are using a profile to do the migration, make sure the Use Cached Exchange Mode box is disabled and that you check any always allow autodiscovery message boxes.

0x8007065e This issue can occur if entries in the network-timeout registry 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 all entries under HKEY_CURRENT_USER\Software\Google\Google Apps Migration\Other have the REG_DWORD registry data type.

IMAP Error: stream error - socket could not be read or written This error is usually related to timeout and connection issues. GWMME retries the migration up to 10 times before it times out.

You can try:

  • Reducing the batches of migrations you're running at one time.
  • Increasing the speed of your network.
  • Increasing the connection to external networks.

For details, see the GWMME Admin Guide.

Permanent failure: BadAttachment

Invalid RFC 822 Message

These errors won't halt the migration but might exist in the logs if some messages fail. Messages usually fail because they don't meet the requirements for Google Workspace.

The GWMME Show Report function provides a full report of messages that failed to migrate. For details on migration reports, see the GWMME Admin Guide.

Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.

Was this helpful?

How can we improve it?
Clear search
Close search
Google apps
Main menu
Search Help Center