Causes This usually related to timeout and connection issues. GSMME retries the migration up to 10 times before it times out. Fixes Step 1: Reduce The Batches Reduce the batches of migrations you’re running at one time. Step 2: Increase The Speed Increase the speed of your network. Step 3:…
Causes Encountered a file that violates Google’s message size restriction, which is likely caused by an attachment that exceeds 25 MB after it’s encoded on the legacy system. Fixes N/A
***Disclaimer : it is also known as Invalid RFC 822 Message Causes The migration wont be halted but might exist in the logs if some messages fail. Messages usually fail because they don’t meet the requirements for G Suite. Fixes Step 1: Access GSMME Show Report Function Access the GSMME…
Causes 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). Fixes Step 1: Use Registry Editor 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…
Causes This error can safely be ignored as GSMME continues to migrate the objects without the missing field. Fixes Step 1: Create A New Administrator Account If you’re experiencing problems, try to create a new administrator account in Exchange. Step 2: Ensure Right Box Is Disabled If you already did…
Causes Related to the legacy administrator not having the required permissions. Fixes Step 1: Create A New Administrator Account Create a new administrator user on Exchange and give the account full mailbox access for all user accounts. Step 2: New Account For Migration Then, use the new account for the…
Causes some files which need to be accessed by GSMME can’t be found. Fixes Step 1: Ensure Outlook Is Installed Ensure Outlook is installed on the system (refer GSMME system requirements) Step 2: Ensure Resource Are Accessible Ensure the user list, resource files, and PST files or folder paths are…
Causes Migration failed because some files couldn’t be found by GSMME. This usually happens due to: The source server couldn’t be found. The usernames specified don’t exist. Outlook isn’t installed or is an unsupported version. Fixes Step 1: Inspect Server Settings Check the server settings and authentication details. Step 2:…
Causes The MAPI message could not be translated to MIME format. Fixes Step 1: Ensure Outlook Is In Latest Version 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.
***Disclaimer: it is also known as 0x80041065, INVALID_CONSUMER_KEY HTTP/1.1, 401 Token invalid Causes An invalid domain consumer secret was specified during configuration In some cases, this error can be caused by clock synchronization. Fixes Step 1: Reinspect The Consumer Secret Recheck the consumer secret in your domain’s Google Admin console….