Clear search
Close search
Google apps
Main menu

Google Apps is now G Suite. Same service, new name. More about the name change.

GSMME error codes

You may encounter the following error messages when using G Suite Migration for Microsoft® Exchange (GSMME). For complete information on using GSMME see Migrate from Microsoft Exchange.

Error code Explanation

This issue is generally benign. However, if it's causing problems, install the latest service packs for your Microsoft Exchange server and Windows® environment. See GSMME system requirements for details. 

If you're still experiencing problems, see Troubleshoot GSMME.


Fail:While stamping the message

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

The only negative consequence is that if the migration is re-run at a later time with the Only New Data box checked, the tool will attempt to migrate the message again because it doesn’t have a record of them. This might lead to duplicate calendar events and contacts.

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


This issue can occur when the user conducting the migration has insufficient privileges to access the PST file or when GSMME is unable to find or access the PST file. GSMME 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 and you should check whether the specified 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 (MBA) 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.








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

If not, 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 may relate to autodiscovery issues with Exchange. Create an administrator profile in 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.


The Exchange administrator account used doesn't have sufficient permissions to open user mailboxes. See GSMME system requirements for details. 

Occasionally, there’s a problem with legacy administrator accounts. Create a new administrator user on Exchange and give the account full mailbox access (MBA) 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.

This error code can also occur if your Exchange server exceeds the MAPI session limit during a migration. You can resolve the issue by configuring GSMME or your Exchange server. See the GSMME Administration Guide for details. 

0x80040154 The most common cause of this error is an incompatible version of Outlook. Try running GSMME on a machine that uses an older version of Outlook, such as Outlook 2010 (32-bit version). 

This is caused by exceeding the 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 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 that has 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 GSMME attempted to update a message in G Suite 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 GSMME encountered a quota limit when connecting to Exchange.

See this Microsoft article for instructions on resolving the issue on your Exchange server. After you make any required changes, try the migration again.

A user is not valid.

Identify the affected user in the trace file (the username will be near the number 80041001). Then, check that the specified user exists in G Suite and isn't suspended or disabled. If needed, see Restore a suspended user.


Invalid/non-existent Google User

At least 1 migrating user is not an existing G Suite user or can't be accessed in G Suite by GSMME. 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 that the user exists in G Suite. Ensure the domain name is correct and isn’t an alias.
  • Ensure that 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. See Create a control CSV file for details. 
  • Verify your OAuth consumer key is enabled.
  • Check that all API scopes specified in the GSMME administration guide are explicitly enabled. Migrations to secondary domains require that the OAuth scopes must be explicitly authorized in the Admin console.




HTTP/1.1 401 Token invalid

An invalid domain consumer secret was specified during configuration. Recheck the consumer secret in your domain's Google Admin console. See Migrate data from Exchange using GSMME for details. 

In some cases, this error can be caused by clock synchronization. Check the timezone specified on the host machine and ensure that Windows is synchronized to Internet time servers. 

Communication to the server failed. You'll see a "Server is busy. Please try again later" message.

Try running the migration again. 

0x80041194 GSMME 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.
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 GSMME. 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.



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

Ensure that Microsoft Outlook® is installed on the system (see 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 (MBA) for all user accounts. Then, use the new account for the migration. You can delete the new administrator account after the migration is complete.

This error can safely be ignored because GSMME will continue 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 Cached Exchange mode is disabled and that you check Always allow for any autodiscovery message boxes. 


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 that 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. GSMME retries the migration up to 10 times before it halts.

You can try:

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

See the GSMME Administration Guide for details. 

Permanent failure: BadAttachment

Invalid RFC 822 Message

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

The GSMME Show Reports utility provides a full report of messages that failed to migrate. For details on migration reports, see the GSMME Administration Guide


Was this article helpful?
How can we improve it?
Sign in to your account

Get account-specific help by signing in with your G Suite account email address, or learn how to get started with G Suite.