GWSMO error codes & messages

Google Workspace Sync for Microsoft Outlook

You might encounter the following error codes and messages when using Google Workspace Sync for Microsoft Outlook (GWSMO). Error codes are located in the GWSMO tracing logs.

Try the Log Analyzer

Submit your trace logs to the Google Admin Toolbox Log Analyzer. Most issues can be identified within a few moments of submission.

Errors & messages

GWSMO error codes
Error code Description
0x00040680 The conversion of a calendar invite from Google Calendar format to Microsoft Outlook format was unsuccessful. To resolve this issue, delete and recreate the event.
0x80004005 A generic error code, which might or might not indicate a problem. Check the tracing log files for more information about the issue.
0x8000ffff Your network is unable to reach Google.com or it timed out when sending an email. Contact your network administrator for assistance.
0x80040109 There might be a problem with your anti-virus software, or another application, which is preventing access to the user's PST files. Turn off these applications temporarily to learn if it resolves the issue. If it does, exclude the PST directory from your anti-virus scans.
0x8004010d The disk is full or the client computer is using a FAT32 file system, which can't handle files larger than 4 GB. Try setting the mailbox size limit to 1 GB and re-syncing. For details, go to Set a local mailbox size.
0x80040111 The source profile for your import seems to have been deleted. Cancel the import or create a profile. For details, go to Recreate or replace your profile.
0x80040116 The languages of the Outlook profiles you're using to import don't match. Update to a more recent version of GWSMO. For details, go to Install GWSMO.
0x80040600
0x80040119
The PST file holding the current user profile is corrupt. To fix this, consult your Microsoft documentation on how to repair PST files.
0x8004060c Your PST file size is too large for Outlook. Create a profile with a smaller size limit. For details, go to Recreate or replace your profile and Set a local mailbox size.
0x80040610 You have an email in your Outbox that is too large. Delete the email or edit it to be smaller.
0x80040811 Your calendar is too large for Outlook to display. If the following registry key is present, remove it:

HKEY_CURRENT_USER\Software\Microsoft\Office\version-number\Outlook\PST\UseLegacyCacheSize

0x800411f4

This error usually means a Microsoft Exchange message store and a GWSMO message store exist in the same profile. Storing both accounts in the same user profile isn't supported.
0x800411f5

Google servers detected messages that can't be handled. These messages might contain a virus or there might be duplicates.

  • Messages with a virus–If you suspect a virus on a client computer or if the error continues, run an anti-virus scan.
  • Duplicate messages–This error clears after a few minutes.
0x800411fb

This issue typically occurs when synchronizing a Gmail label. It can happen if a folder with the same name exists in Outlook. To review the error, check the Sync Issues > Local Failures folder in Outlook.

To fix this issue, rename the Gmail label. For more details on editing Gmail labels, go to Create labels to organize Gmail.

0x80070002

When this error code appears as "GetMAPISVCPath @ 168 ()> Failed with 0x80070002", it typically means Outlook isn't installed, or the Microsoft Windows Store version of Outlook is installed.

To fix this issue, consult your Microsoft documentation on how to download and install Microsoft Office.
0x80070005 This issue typically occurs when there’s a configured limit to the PST file size. Consult your Microsoft documentation for information on how to set up the size limit for PST files in Outlook.
0x8007000e

This issue typically occurs when there is not enough storage available to complete the operation.

To fix this issue, make sure the system isn't overloaded by checking the following resources:

  • Ensure there's enough free disk space and memory.
  • Ensure there aren't too many processes running for your system.
  • Ensure no other programs are using the PST. For example, other email add-ons, other programs with Outlook integrations, anti-virus programs, etc.
0x8007007e

This issue typically occurs if:

  1. GWSMO couldn't load the required Outlook libraries (MAPI DLLs). If this error is present, it typically appears in GWSMO's trace log files. To fix this issue, repair your Office installation. If the issue persists, uninstall and reinstall Office.
  2. Outlook is unable to load the correct gsync32.dll file. If this error is present, it typically appears in Outlook. Verify the only copy of gsync32.dll on your system is in C:\Program Files\Google\Google Apps Sync or C:\Program Files (x86)\Google\Google Apps Sync. Then, make sure you have permission to execute it.
0x800704dc Sign in authentication was unsuccessful. The error code means there's a configuration issue on the computer. You might need to re-register your DLLs on the client computer. Consult your Microsoft documentation on how to do it.
0x80070482

One of the DLL files needed to run this application is corrupt or you might be running an outdated version of the DLL. To resolve the issue, uninstall and reinstall GWSMO. For details, go to Install GWSMO.

0x8007065e

This issue can occur if the network timeout registry entries were created using the wrong registry data type. For example, REG_SZ instead of REG_DWORD.

  1. To fix this:
    1. In the Start menu, click Windows Systemand thenRun.

      Note: Alternatively, press the Windows key + R.

    2. In the Run box, enter regedit.
    3. Click OK.
  2. Go to HKEY_CURRENT_USER\Software\Google\Google Apps Sync\Other.
  3. Make sure all values are of type REG_DWORD and not any other type.

For details on working with the registry, go to Configure options through the registry.

0x8007273d Winsock is corrupt on the client computer. Consult your Microsoft documentation on how to resolve this.
0x80072ee2
0x80072ee7
0x80072efd
0x80072efe
0x80072ee0
0x80072f94
GWSMO is experiencing network timeouts. Extend the timeout period by modifying your registry. For details, go to Large messages time out over a slow connection.
0x80072f78 GWSMO is unable to sync some of your email. The reason is likely due to network issues or large messages. For details, go to Large messages time out over a slow connection.
0x80072f8f

This issue occurs if:

  • The time is set incorrectly on the local machine.
  • The local certificate store is incorrect.
  • A proxy or firewall configuration is blocking GWSMO.

Check for these issues on the host machine.

0x80be000b
0x80041004

The email database for GWSMO is corrupt. A crash on the client computer while GWSMO is syncing usually causes this issue.

Remove and reinstall the current profile. For details, go to Recreate or replace your profile.

GWSMO error messages
Error message Description
Can't handle conflicting folder (): Contacts If you update a contact from both Outlook and Google Workspace, or a mobile device, a conflict can occur because GWSMO keeps 2 versions of the contact. You won't lose any data when this happens as both versions of the contact are kept. For details, go to Does data still sync when you get a conflict error?
Cannot open your default email folder...MAPI was unable to load the information service gsync.dll Search your system for the gsync32.dll file and remove any duplicates. Or, you can reinstall Outlook.
CryptUnprotectData failed with 0x8009000b Decrypting stored credentials failed.

A known issue with the "HP Customer participation utility task" on Windows 10 related to Outlook and other apps not remembering your password after a Windows update is usually the cause of this issue. To fix this, consult your Microsoft documentation for a workaround to this issue.

E:FreeBusy gsync32!FreeBusyServer::
ValidateOutlookFreeBusy
Config

The logs indicate that Free/Busy functionality doesn't work due to local settings.

  1. To fix this:
    1. In the Start menu, click Windows Systemand thenRun.

      Note: Alternatively, press the Windows key + R.

    2. In the Run box, enter regedit.
    3. Click OK.
  2. Go to HKLM\SOFTWARE\Microsoft\Office\your-version-number \Outlook\SchedulingInformation\FreeBusySupport.
  3. Set the value of SMTP to {0006F049-0000-0000-C000-000000000046}.

For details on working with the registry, go to Configure options through the registry.

error: .vir. The server won't send some messages with attachments because it detects a virus. Scan for viruses to resolve this issue.
GLOOK_NO_SYNCER_
FOR_MSG_STORE_FOR
_XP_PROVIDER
This error usually means an Exchange message store and a GWSMO message store exist in the same profile. Storing both accounts in the same user profile isn't supported.
HTTP/1.1 401 Service disabled by Google Workspace admin Google Calendar service isn't turned on for your domain in the Google Admin console. For details, go to Turn Calendar on or off for users.
HTTP/1.1 403 This domain does not allow users to access the Email Migration API. To fix this issue, you need to turn on API access in the Google Admin console.
HTTP/1.1 413 Request Entity Too Large A web proxy or another network system is blocking large requests. Make sure your network is set up to allow these requests. For further details, review your proxy logs.
HTTP/1.1 502 Bad Gateway GWSMO is experiencing network timeouts. Extend the time-out period by modifying your registry. For details, go to Large messages can time out over a slow connection.
HTTP/1\.1 500 Internal Server Error There might be transient connectivity issues with Google servers. Verify you're able to connect to http://mail.google.com/a/domain name. If you can connect without issue, ensure the following URLs are available on your network through port 443:
  • Signing: https://www.google.com/accounts/ClientLogin
  • Calendar: https://www.google.com/calendar/feeds
  • Contacts: https://www.google.com/m8/feeds/contacts/
  • Email: https://mail.google.com/a/domain/r/
  • Email Migration: https://apps-apis.google.com/a/feeds/migration/2.0/[domain]
If your computer can contact those URLs and you're able to access mail from the web, then you need to contact Google Cloud Support for further help.

LogPotentialProxyNetwork
Failure

HTTP/1.1 400 Bad Request

You might be using a network proxy. Proxies aren't supported with GWSMO. Ensure all traffic is allowed on port 443 for Outlook.exe and ProfileEditor.exe.
MAPI was unable to load the information service gsync\.dll

There might be a few causes for this problem. Verify the following:

  • Make sure the only copy of the gsync32.dll file on your system is located in C:\Program Files\Google\Google Apps Sync.
  • Make sure the affected user has read/execute permission in that directory.
  • Verify the client computer has the folder C:\Program Files\Common Files\System\MSMAPI\1033\.
  • Restart the system.
  • Ensure the DLL files are associated with Microsoft Office.

If the above steps don't resolve the issue, uninstall and reinstall Outlook and GWSMO.

MAPIToMIMEStm threw exception with message The MAPI-to-MIME conversion of one or more of your email messages was unsuccessful. Try to send the message again. If the issue persists, reinstall Outlook.
Max file size The affected user has reached the mailbox size limit set in GWSMO. If the user wants to synchronize their entire mailbox, they must set the limit to Unlimited. For details, go to Set a local mailbox size.
Permanent failure: BadAttachment The logs indicate you’re trying to send attachments that Gmail doesn't support. For details, go to Executable file attachments aren't appearing.

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?