Causes At least one migrating user doesn’t exist in your G Suite account or can’t be accessed in G Suite. Fixes Find the affected user in the logs and check the following for the user: Step 1: Verify The User Existence Verify in the Google Admin console the user exists…

Causes A user is not valid Fixes Step 1: Identify The User Identify the user in the trace file (the username is near the number 80041001). Step 2: Check For User Existence Then, check if the specified user exists in G Suite and isn’t suspended or disabled. Step 3: Restore…

Causes GSMME encountered a quota limit when connecting to Exchange Fixes Step 1: Consult Microsoft Documentation Consult Microsoft documentation for more information on how to configure named properties and replica identifier quotas. Step 2: Try Migration Again After any required changes is made, try the migration again.

Causes GSMME attempted to update a message in G Suite but failed,  as the system is trying to migrate mail that’s already migrated but was moved post-migration. Fixes This error is not fatal as the mail is already undergo migration.

Causes due to the exceeding 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. Fixes Step 1: Migrating User With A PST File To resolve the…

Causes an incompatible version of Outlook Fixes Step 1: Run GSMME Using Older Version Try running GSMME on a machine using an older version of Outlook, such as Outlook 2010 (32-bit version)

Causes The Exchange administrator account doesn’t have sufficient permissions to open user mailboxes. This error code can also occur if your Exchange server exceeds the MAPI session limit during a migration. Fixes Step 1: Create A New Administrator User Create a new administrator user on Exchange and give the account…

*** Disclaimer : also known as 0x80072ee0, 0x80072ee2, 0x80072ee7, 0x80072ef3, 0x80072efd, 0x80072efe, 0x80072f94 Causes GSMME encountered network timeouts while attempting to connect or upload messages to Google servers due to inaccessible network or if there’s a slow network connection. the error might relate to autodiscovery issues with Exchange. (if 1stand…

Causes 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…

Causes Another process (such as anti-virus, desktop search or backup software) is accessing GSMME’s database file during the migration, causing the tool aren’t able to save a record of the message migration. It might lead to duplicate calender events and contacts if the migration is re-run at a later time…