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
This tool can identify most issues within a few moments of submission.
- Submit your trace logs (as uncompressed or ZIP files) to the Google Admin Toolbox Log Analyzer.
- For advanced log analysis, submit uncompressed files to Log Analyzer 2.
Get details on where to find your trace log files.
Errors & messages
Expand all | Collapse all & go to top
GWSMO error codes| Error code | Description & troubleshooting steps |
|---|---|
| 0x00002f94 |
GWSMO failed to autodetect a proxy. If you aren't using a proxy or you aren't facing connectivity issues, you can ignore this code. If you are using a proxy, make sure it's set up correctly in Windows. To check, from the Windows Start menu, click Internet Options |
| 0x00040680 | The conversion of a calendar invite from Google Calendar format to Microsoft Outlook format was unsuccessful. To resolve this issue, delete and re-create 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 antivirus 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 resyncing. For details, go to Set a local mailbox size. |
| 0x80040111 | The source profile for your import might be deleted. Cancel the import or create a profile. For details, go to Re-create 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 Get ready & 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 Re-create 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. GWSMO doesn't support having an Exchange account in a GWSMO profile. |
| 0x800411f5 | Google servers detected messages that can't be handled. The messages might contain a virus or there could be duplicates.
|
| 0x800411fb | This issue typically occurs when synchronizing a Gmail label. It's usually when a Gmail label name matches the name of a built-in Outlook folder. To review the error, check the Sync Issues To fix this issue, rename the label on the Gmail web interface so that it no longer conflicts with an existing folder in the GWSMO profile. For more details on editing Gmail labels, go to Create labels to organize Gmail. If that method doesn't work, create another GWSMO profile. However, do not use copy and paste, or dragging, to copy folders from other profiles or accounts. |
| 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 the issue, make sure the system isn't overloaded by ensuring:
|
| 0x8007007e | This issue typically occurs if:
|
| 0x80070018 | If you get this error and an event fails to sync or event invitation emails aren't sent (or remain stuck in the Outbox), check the calendar event description. If it's longer than the maximum 8 KB allowed, delete the description or reduce it in size. |
| 0x800704dc | Sign in authentication was unsuccessful. The error code means there's a configuration issue on the computer. You might need to reregister 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 Get ready & 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.
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, 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 Re-create or replace your profile. |
| Error message | Description & troubleshooting steps |
|---|---|
| Error 400: invalid_request: The version of the app you're using doesn't include the latest security features to keep you protected. Please make sure to download from a trusted source and update to the latest, most secure version | Make sure you're using the latest version of GWSMO. For details, go to Get ready & install GWSMO. |
| 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.
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:
|
| 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:
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 | 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.