AvePoint Docs
Graph API
My support tickets
Graph API
My support tickets
English

    Home > Google Chat Space Related Codes

    Export to PDF

    Google Chat Space Related Codes

    GS-ChatAPIForbidden

    Issue:

    The object failed in the migration with the following error:

    - **GS-ChatAPIForbidden**

    Details:

    The error may occur in the following situations:

    - Situation 1: The admin user does not have permission to manage the destination space. - Situation 2: The destination space is not completed.

    Recommendations:

    For situation 1, ensure the admin user has the Space manager permission and run an incremental or “Retry error objects“ migration job to resolve this issue.

    For situation 2, run a “Complete migration” job to make the destination space available for end users. Then, run an incremental or “Retry error objects“ migration job to resolve this issue.

    GS-DestinationMessageSenderNotInSpace

    Issue:

    The object failed in the migration with the following error:

    - **GS-DestinationMessageSenderNotInSpace**

    Details:

    The destination message sender configured in the user mapping does not exist in the destination space. In this case, the object cannot be migrated due to Google API limitations.

    Recommendations:

    Run a Migration membership job to add the message sender to the destination space and then an incremental job later to resolve this issue.

    GS-EmptyDestinationGoogleGroupEmailAddress

    Issue:

    The object failed in the migration with the following error:

    - **GS-EmptyDestinationGoogleGroupEmailAddress**

    Details:

    The error indicates that you selected to migrate the group mailbox of the source Team, but did not configure the destination Google Group email address in the project mapping.

    Recommendations:

    Configure the Google Group email address in the project mapping and run an incremental or "Retry error objects" migration job later to resolve this issue.

    GS-ExternalUserUnsupportedInDestinationMailbox

    Issue:

    The object failed in the migration with the following error:

    - **GS-ExternalUserUnsupportedInDestinationMailbox**

    Details:

    The error indicates that the source user is mapped to an external user to the destination, but external users cannot be added to the destination Google Group mailbox.

    Recommendations:

    Update the user mapping to map the source user to an internal user of the destination. Then, run an incremental or "Retry error objects" migration job later to resolve this issue.

    GS-FailedToGetUserInformation

    Issue:

    The object failed in the migration with the following error:

    - **GS-FailedToGetUserInformation**

    Details:

    Failed to retrieve the email address of the source external user while mapping the user to a destination user. This error occurs when the external user does not have the Microsoft 365 E5 Developer license.

    Recommendations:

    Contact the tenant administrator of the external user to grant the Microsoft 365 E5 Developer license to the user. Then, run an incremental or "Retry error objects" migration job later to resolve this issue.

    GS-MessageAttachmentReplaceWarning

    Issue:

    The message failed in the migration with the following error:

    - **GS-MessageAttachmentReplaceWarning**

    Details:

    No destination file can be mapped with the attachment. The error may occur in the following situations:

    - Situation 1: The file related to the message does not exist in the source Team site. - Situation 2: The file related to the message failed to be migrated to the destination Google Drive.

    Recommendations:

    For situation 1, configure a URL mapping to map the source attachment to an existing destination file. Then, run a "Replace attachment URLs" job to resolve this issue.

    For situation 2, check the error details of the failed file in the comment of the Migration errors section by navigating to Projects > Project mappings > View migration report > Migration error tab in Fly. Resolve the error according to the details, and run an incremental or "Retry error objects" migration job to migrate the file. After the file is migrated, run a "Replace attachment URLs" job to resolve this issue.

    GS-MessageConflict

    Issue:

    The message failed in the migration with the following error:

    - **GS-MessageConflict**

    Details:

    The message already exists in destination space.

    Recommendations:

    Choose one of the following options to resolve this issue:

    - Delete the conflict message from the destination space and run an incremental or "Retry error objects" migration job to resolve this issue. - Delete the space from the destination, clear the mapping report, and run a full migration job for the source Team.

    GS-MessageFailedByUploadingAttachment

    Issue:

    The object failed in the migration with the following error:

    - **GS-MessageFailedByUploadingAttachment**

    Details:

    The source chat message contains media files (images or videos). In this case, Fly will migrate these media files as destination chat message attachments. The error indicates that an API error occurs while migrating the media files.

    Recommendations:

    Contact Support and provide screenshots of source and destination messages, and the job ID to analyze the error.

    GS-MessageFailedContainNonMediaData

    Issue:

    The object failed in the migration with the following error:

    - **GS-MessageFailedContainNonMediaData**

    Details:

    The chat message contains multiple non-media attachments. Such chat messages cannot be created in the destination due to Google API limitations

    Recommendations:

    Contact Support and provide screenshots of source and destination messages, and the job ID to analyze the error.

    GS-MessageFailedWithFoundUser

    Issue:

    The object failed in the migration with the following error:

    - **GS-MessageFailedWithFoundUser**

    Details:

    This error indicates that the destination space is under the import mode and a Google API error occurs while migrating the message. In this case, Fly will use the destination chat sender to send a blank message to keep the message created time and migrate the message as a placeholder message to the destination to ensure the remaining messages in the source chat can be migrated.

    Recommendations:

    Run an incremental migration job to resolve this issue. If the error persists, contact Support and provide the migration mapping information and job ID to analyze the error.

    GS-MessageFailedWithNotFoundUser

    Issue:

    The object failed in the migration with the following error:

    - **GS-MessageFailedWithNotFoundUser**

    Details:

    The error may occur in the following situations:

    - Situation 1: The destination space is under the import mode and a Google API error occurs while migrating the message. - Situation 2: The chat message sender cannot be found in the destination.

    In these cases, the remaining messages in the source chat cannot be migrated either.

    Recommendations:

    For situation 1, run an incremental migration job to resolve this issue. If the error persists, contact Support and provide the migration mapping information and job ID to analyze the error.

    For situation 2, configure a user mapping for the source chat message sender or enable at least one mapping property to allow Fly to retrieve the sender in the destination. Then, run an incremental migration job to resolve this issue.

    GS-MessageNotSupported

    Issue:

    The object failed in the migration with the following error:

    - **GS-MessageNotSupported**

    Details:

    The message type is not supported in the migration.

    GS-MessageTooLongWarning

    Issue:

    The message has been migrated but has the following error:

    - **GS-MessageTooLongWarning**

    Details:

    The message content has exceeded Google’s allowed limit of 32000 bytes. In this case, the exceeding bytes have been truncated due to Google API limitations.

    Recommendations:

    Check if the key content of the destination message has been truncated. If it has been truncated, modify the source message content to be less than 32000 bytes and run an incremental job to resolve this issue. If not, you can ignore this error.

    GS-PermissionNotMapWarning

    Issue:

    The object failed in the migration with the following error:

    - **GS-PermissionNotMapWarning** - **Details:**

    The mapped destination Google user configured in the user mapping is inactive, does not exist, or an external user.

    Recommendations:

    Update the user mapping to map the source user to an active internal Google user. Then, rerun the migration job.

    GS-RateLimitExceeded

    Issue:

    The object failed in the migration with the following error:

    - **GS-RateLimitExceeded**

    Details:

    Your request has been throttled by Google due to frequent requests.

    Recommendations:

    Choose one of the following options to resolve the issue:

    - Reduce the number of jobs running simultaneously. - Run the jobs at off-peak hours. - Split the scope of a job into multiple jobs.

    GS-ReplyRateLimitExceeded

    Issue:

    The object failed in the migration with the following error:

    - **GS-ReplyRateLimitExceeded**

    Details:

    The number of replies in the destination space has exceeded Google’s allowed limit of 500.

    Recommendations:

    Manually delete some destination replies and run an incremental or "Retry error objects" migration job to resolve this issue.

    GS-SkipNotChangeData

    Issue:

    The member has been skipped with the following information:

    - **GS-SkipNotChangeData**

    Details:

    The information indicates that the member already exists in the destination.

    GS-SkippedDuplicateDestinationMember

    Issue:

    The object failed in the migration with the following error:

    - **GS-SkippedDuplicateDestinationMember**

    Details:

    The member already exists in the destination space.

    GS-SpaceGuidelineExceedLimit

    Issue:

    The object failed in the migration with the following error:

    - **GS-SpaceGuidelineExceedLimit**

    Details:

    The destination space guidelines exceed the maximum character limit.

    Recommendations:

    Ensure the guidelines do not exceed 4900 characters and run a "Retry error objects" migration job to resolve this issue.

    GS-SpaceHasErrorMessage

    Issue:

    The object failed in the migration with the following error:

    - **GS-SpaceHasErrorMessage**

    Details:

    Failed to migrate the message related to the chat.

    Recommendations:

    Navigate to Projects > Project mappings > View migration report > Migration error tab in Fly to view the failed message in the comments of the chat in the Migration errors section. Resolve the error for the message according to the details, and run an incremental or "Retry error objects" migration job to migrate the chat.

    GS-SpaceHasMappedByASource

    Issue:

    The object failed in the migration with the following error:

    - **GS-SpaceHasMappedByASource**

    Details:

    The destination space has already been mapped by another source channel.

    Recommendations:

    Modify the destination space name in the channel mapping and run a "Retry error objects" migration job to resolve this issue.

    GS-SpaceIsBlocked

    Issue:

    The channel failed in the migration with the following error:

    - **GS-SpaceIsBlocked**

    Details:

    The destination space has been blocked. In this case, the source messages, memberships, and channel settings cannot be migrated.

    Recommendations:

    In Google Chat, navigate to Settings > Access Restrictions > Manage blocked spaces to unblock the destination space. Then, run an incremental or "Retry error objects" migration job to resolve this issue.

    GS-SpaceNotComplete

    Issue:

    The object failed in the migration with the following error:

    - **GS-SpaceNotComplete**

    Details:

    The destination space is incomplete and unavailable for destination users.

    Recommendations:

    Run a “Complete migration” job to make the destination space available for end users. Then, rerun the job to resolve this issue.

    GS-UserInArchived

    Issue:

    The object failed in the migration with the following error:

    - **GS-UserInArchived**

    Details:

    The destination Google user configured in the user mapping is archived.

    Recommendations:

    Unarchive the destination Google user, or update the user mapping to map the source user to an active Google user. Then, rerun the migration job.

    GS-UserInSuspended

    Issue:

    The object failed in the migration with the following error:

    - **GS-UserInSuspended**

    Details:

    The destination Google user configured in the user mapping is suspended.

    Recommendations:

    Reactivate the destination user or update the user mapping to map the source user to an active Google user. Then, rerun the migration job.