You might encounter the following error codes and messages when using G Suite Migrate.
Data errors | Service errors | Migration errors | Crawl errors | Commit errors | Action errors | Bridge data errors | Bridge execution errors | Google connection errors | Bridge processing errors | ABBadRequest errors
You might see this issue when trying to edit a template. The template doesn’t load.
To resolve the issue, choose an option:
|0||DisposalError||An error occurred while removing unused resources.|
|1||NoDataReturned||No data was returned from the provider. Check service host log for details.|
|2||UnexpectedDataAccessError||An unexpected error occurred accessing the data provider.|
When you run a migration, you might see these errors in the execution log.
|400||Bad Request||There is data corruption in the source environment. The source data causing the issue is probably defective.
If you want to keep the data, analyze which objects are affected and move them manually to your G Suite account. For details on how to manually move objects, consult your source data documentation.
G Suite Migrate doesn't have the required access to a source or target system.
During a Microsoft Exchange migration, you might see this error:
|403||Forbidden||Either a G Suite service (such as Gmail or Google Drive) isn't enabled or you have exceeded your daily API quota levels.
Turn on the G Suite service in the Google Admin console. If the issue relates to quotas, apply for a higher quota level in the Google Cloud Platform Console. Or, wait until the following day to proceed.
|410, 5xx||Gone||Transient errors.
Run a delta migration. If the error persists, contact G Suite support.
|429||Too Many Requests||
The migration is overloading a source or target system with too many requests.
Determine which service is overloaded and, if possible, increase the service limits.
|5000||CouldNotGetSerializedData||A serialized element couldn't be loaded for the given transaction.|
|5001||BridgeObjectDoesNotExist||No object with the specified ID could be found.|
|50000||InheritedPermissionNotFound||The permission was expected to be inherited, but was not detected. The transaction failed to ensure that the permission was inherited.|
|50001||GoogleUploadTimeout||There was a timeout while uploading a file.|
|50002||GoogleServiceUnavailable||The Google service is not available.|
|50003||TemporaryFolderCreationFailed||Could not provision a temporary folder for the creation of data with an unknown parent.|
|50004||ExistingDocumentHandlingFailed||Information from an existing document couldn't be copied to the replacement file.|
|50005||GoogleQueryFail||An error occurred while running the query.|
The sharing right being added didn't correspond to a Google Account. Sharing with this user requires that email notifications are allowed.
To do this, enable Allow email invitations in the settings template.
|50007||DomainDoesNotAllowSharingRight||The requested sharing right isn't allowed by the domain. For help, contact your domain administrator.|
|50008||WriteAccessDenied||Unable to assign write access for the modifying user.|
|50009||DomainTransferFileCopyFailed||The domain transfer file copy couldn't be completed.|
|50010||MetadataUpdateFailed||An error occurred finalizing metadata.|
|50011||RenameFileFail||An error occurred when renaming the file.|
|50012||SetModifiedFailed||The last modified date couldn't be set.|
|50013||InsertParentFail||Adding the parent folder reference failed.|
|50014||SyncPermissionsFail||Failed to synchronize permissions.|
|50015||ICalConflictsWithUnknownEvent||The imported event's iCal ID conflicts with an existing but unknown event.|
|50016||NoSuperAdminsWithCalendarAccess||No super administrator accounts have the Google Calendar service enabled. For more information, read the Calendar resources–Super administrator accounts watchpoint in the Watchpoints table.|
|1048577||NoResponse||No response service was provided.|
|1048578||Unauthorized||The connector isn't authorized for that request.|
|1048580||MissingRequestType||No request type was defined for this request element.|
|1048584||TooManyRequestTypes||Only one request type may be specified for a single object fetch.|
No object was found at the specified location.
If you're migrating from Microsoft SharePoint, make sure you've created a location list that includes the affected location. Then, add the list to your connection.
|1048608||LocationTypeMismatch||The object found at the specified location was not of the expected type.|
|1048640||ReadOnlyType||The request type does not allow write operations.|
|1048704||TooManyResponses||The request returned a collection when a single value was expected.|
|1048832||RequestConversionError||Type conversion failed for this request.|
|1049088||SerializationError||Could not serialize converted type objects.|
|1049600||ResponseRoutingError||The response service received an unexpected request.|
|1050624||ConnectionUnavailable||The requested connection is unavailable.|
|1052672||DispatchFailed||The intended response service was initially found, but the request could not be dispatched.|
|1056768||TryAgainLater||The request could not be completed at this time. You should try again later.|
|1081344||InvalidWriteContext||The request could not be written in the current context.|
|1114112||InvalidElementData||The supplied element did not specify required data.|
A request for additional data failed.
You might see this error if you're trying to migrate files from SharePoint that are larger than 2 GB.
Make sure that the node servers have sufficient space available. The nodes must have more free space than the size of the largest file you're migrating. For more details on SharePoint file sizes, go to Large items.
|1572864||RequestInvalidated||The requesting service was invalidated.|
An internal connector error occurred. You might see this error if you have more than the maximum number of display lookup columns defined for a SharePoint list.
|3145728||InvalidRequest||An internal connector error occurred.|
|5242880||InvalidAction||A request for an unrecognized action was sent to a connector. You might see this if you have mismatched versions of platform and nodes, and a new action is sent to an old node.|
|9437184||SkippedByContext||A transaction has been skipped. It has been marked with this code for identification purposes.|
|17825792||WarnedByContext||The request could not be completed. Some data might not have been written correctly.|
|34603008||InvalidImport||The specified import string was invalid.|
|68157440||ResolvedByContext||A request was made to change an object that already exists and is unable to be changed. No action was taken.|
If there’s a problem that you cannot resolve, contact G Suite support. For details, see the section Still need help? in Troubleshoot G Suite Migrate.
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.