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

Home > Microsoft 365 Group Related Codes

Export to PDF

Microsoft 365 Group Related Codes

TG-APPInitChannelFolderFailed

Issue:

The channel failed in the migration with the following error:

- **TG-APPInitChannelFolderFailed**

Details:

The error may occur in the following situations:

- The source channel is a private/shared channel, and the corresponding site collection of the private channel/shared is not created. - The destination channel does not exist before the migration, and you only use the app profile method to connect the destination to Microsoft 365. Due to the API limitation, the account of the app profile can create the channel in the destination but cannot create the corresponding site collection of the private/shared channel or folder of the standard channel. Therefore, data in the source channel cannot be migrated to the destination channel. - The source channel cannot be retrieved since the approval status of the channel folder is **Pending**.

Recommendations:

Refer to the following methods to resolve this issue:

- If the SharePoint site collection for the source private/shared channel is not created, you can access the **Files** tab of the source channel to initialize the site collection for the source channel, and then rerun the job to migrate the channel. - If the SharePoint site collection for the destination private/shared channel is not created in the migration, you can manually click the **Files** tab of the channel to initialize the site collection for the destination channel, and rerun the migration job to migrate the source data to this channel. - To ensure that the channel data can be migrated, make one of the following preparations before the migration: - Provide a service account in the destination connection if the destination channel does not exist. - Make sure the destination channel already exists if a service account cannot be provided. - Manually update the approval status of the channel folder to **Approved**, and run the migration job to migrate the channel.

TG-CannotModifyRoleSinceShortDuration

Issue:

The group role failed in the migration with the following error:

- **TG-CannotModifyRoleSinceShortDuration**

Details:

This error occurs when you just modified the role and then modified it again before the update was synchronized.

Recommendations:

Please wait for a few minutes and try again.

TG-CanNotPostTaskComment

The task failed in the migration with the following error:

- **TG-CanNotPostTaskComment**

Details:

Task comments cannot be posted to the destination tenant.

Recommendations:

Try adding task comments to a Planner task in the destination to see if it works natively. If not, please contact Microsoft for support.

TG-ChannelNameNotAllowed

Issue:

The channel failed in the migration with the following error:

- **TG-ChannelNameNotAllowed**

Details:

The destination channel name is blocked by Microsoft since the name has invalid characters or the name length exceeds Microsoft’s allowed limit.

Recommendations:

Update the destination channel name in the channel mapping, and rerun an incremental or "Retry error objects" migration job.

TG-CustomDocumentLibraryNotFound

Issue:

The document library tab failed in the migration with the following error:

- **TG-CustomDocumentLibraryNotFound**

Details:

The document library tab failed to be migrated since the tab is linked to a custom document library of the team site that cannot be found in the destination.

Recommendations:

Refer to the following options to resolve this issue:

- Manually create a document library in the destination using the same library name as the source document library, and rerun a migration job to migrate the failed tab. - If you want Fly to migrate the custom document library, refer to the following steps: 1. Make sure the **Only** **the default** **Documents library**checkbox is deselected in the migration policy to ensure that the custom document library can be migrated. 2. Rerun the migration job to migrate the tab. In details: In Teams migration, Fly will start three jobs in the backend to respectively migrate data in source Teams, data in team sites, and data in group mailboxes, and the job to migrate data in source Teams will start first. Then, if the custom document library is migrated in the current job, only rerun the migration job once to migrate the failed tab; if the custom document library has not been migrated in the current job, rerun the migration job twice.

TG-FailedToHandleGroupRoleSinceCredential

Issue:

The group role failed in the migration with the following error:

- **TG-FailedToHandleGroupRoleSinceCredential**

Details:

The error occurs when the source/destination connection does not have a custom app profile or a custom delegated app profile configured in it.

Recommendations:

Make sure a custom app profile or a custom delegated app profile with the required permissions is configured in both the source and destination connections. Then, run an incremental or "Retry error objects" migration job later to resolve this issue.

TG-GroupNotFound

Issue:

The Team failed in the migration with the following error:

- **TG-GroupNotFound**

Details:

The error indicates that the source Team cannot be found.

This error may occur in the following situations:

- The source Team has been deleted from the Microsoft 365 tenant. - The source Team email address in the migration mapping is incorrect. - The source Team address is an alias that is unsupported in the migration.

Recommendations:

- If the source Team has been deleted from the Microsoft 365 tenant, delete the Team mapping from the migration project. - Make sure the source Team email address configured in the migration mapping is correct. - Update the Team alias in the migration mapping to the primary email address.

TG-GroupTeamSiteNotFound

Issue:

The Team/Group failed in the migration with the following error:

- **TG-GroupTeamSiteNotFound**

Details:

The error indicates that the team site of the source Team/Group cannot be found.

This error may occur when the team site of the source Team/Group has been deleted.

Recommendations:

- Check whether the team site of the source Team/Group is deleted. If the site exists, rerun the migration job.

TG-MaximumBucketsInPlan

Issue:

The bucket failed in the migration with the following error:

- TG-**MaximumBucketsInPlan**

Details:

The number of buckets exceeded the allowed limit of 200.

Recommendations:

- Check the number of buckets of the destination plan and remove the invalid buckets. Then, try again.

TG-MaximumTasksCreatedByUser

Issue:

The task failed in the migration with the following error:

- TG-MaximumTasksCreatedByUser

Details:

The task failed to be migrated since the number of tasks created by the destination service account exceeded Microsoft’s allowed limit.

Recommendations:

Update the destination connection to use a different service account, and rerun an incremental or "Retry error objects" migration job.

TG-MaximumTasksAssignedToUser

Issue:

The task failed in the migration with the following error:

- TG-**MaximumTasksAssignedToUser**

Details:

The number of tasks assigned to a user has exceeded the allowed limit of 3000.

Recommendations:

Check the number of tasks of the destination users and remove the invalid tasks. Then, try again.

TG-MissingPermission

Issue:

The object failed in the migration with the following error:

- **TG-MissingPermission**

Details:

The object failed to be migrated since the app profile/service account does not have sufficient permissions.

Recommendations:

Refer to or to grant the app profile/service account with required permissions, and rerun an incremental or "Retry error objects" migration job.

TG-MissingPermissionToLoadAviatorData

Issue:

The object failed in the migration with the following error:

- **TG-MissingPermissionToLoadAviatorData**

Details:

The app profile / service account / delegated app profile does not have sufficient permissions.

Recommendations:

Refer to or to grant the app profile / service account / delegated app profile required permissions, and try again.

TG-NeedApp

Issue:

The tag failed in the migration with the following error:

- **TG-NeedApp**

Details:

The error indicates that there is only a service account used in the source or destination connection.

Recommendations:

Make sure both the source and destination connections have an app profile, and rerun an incremental or "Retry error objects" migration job.

TG-NeedAppOrDelegateAppForTag

Issue:

The tag/Team failed in the migration with the following error:

- **TG-NeedAppOrDelegateAppForTag**

Details:

Tags cannot be migrated if you only use the service account to connect to the tenant.

Recommendations:

Provide an app profile or a delegated app profile for the source and destination connection, and run an incremental job.

TG-NeedAppToBackup

Issue:

The object failed in the migration with the following error:

- **TG-NeedAppToBackup**

Details:

The object cannot be migrated if only use the service account to connect to the source tenant.

Recommendations:

Provide an app profile for the source connection, and rerun the migration job.

TG-NeedDelegateAppForTagInGCCH

Issue:

The tag failed in the migration with the following error:

- **TG-NeedDelegateAppForTagInGCCH** - **Details:** - Tags in a Microsoft 365 Government GCC High tenant cannot be migrated without a delegated app profile. - **Recommendations:**

Provide a delegated app profile for the connection, and rerun the migration job.

TG-NeedInitialization

Issue:

The object failed in the migration with the following error:

- **TG-NeedInitialization**

Details:

The error indicates that the source object has not been initialized.

Recommendations:

Manually initialize the object in the source, and rerun an incremental or "Retry error objects" migration job.

TG-NeedRightSendEmails

Issue:

The task failed in the migration with the following error:

- **TG-NeedRightSendEmails**

Details:

The destination service account does not have an Exchange Online license and cannot send emails.

Recommendations:

Assign an Exchange Online license to the destination service account and make sure the service account can send emails, and rerun the migration job.

TG-OrderHintOverflow

Issue:

The task or bucket failed in the migration with the following error:

- **TG-OrderHintOverflow**

Details:

During the migration, the source order of buckets and tasks needs to be migrated. The order is controlled by an attribute called OrderHint, which is a randomly generated string by Microsoft. When there are a large number of buckets or tasks, the OrderHint string may exceed the length limit, causing the migration failure.

Recommendations:

Run an incremental migration job.

TG-PlanIsNotMigrate

Issue:

The Planner tab failed in the migration with the following error:

- **TG-PlanIsNotMigrate**

Details:

The error may occur in the following situations:

- Situation 1: The Planner tab failed to be migrated since the tab's plan is not migrated. - Situation 2: The Planner tab is added or converted from project (premium planner). In this case, the Planner tab cannot be migrated.

Recommendations:

For situation 1, go to the Migration errors section of the migration mapping for details about the plan, and make sure the plan can be migrated with the tab. Then rerun an incremental or "Retry error objects" migration job.

For situation 2, you can manually add the tabs to the destination.

TG-TeamAppNotFound

Issue:

The app/tab failed in the migration with the following error:

- **TG-TeamAppNotFound**

Details:

The error may occur as:

- When migrating an app, Fly checked that the app does not exist in the destination Teams app store. - When migrating a tab, Fly checked that there is no app installed in the destination Teams that can be associated with the tab. Since you also deselect **Apps** in the migration policy in Fly, Fly cannot install the app to the destination Team.

Recommendations:

- For the first case, manually upload the app to the destination Teams app store, and rerun the migration job. Fly will install the app to the destination Team. - For the second case, select **Apps** in the migration policy, and rerun the migration job. Then if the app exists in the destination Teams app store, Fly will install the app to the destination Team and migrate the tab to the destination channel.

TG-TenantAccessDenied

Issue:

The Team failed in the migration with the following error:

- **TG-TenantAccessDenied**

Details:

The error may occur as follows:

You use the service account authentication to access the Team, but the service account is not the Teams Service Administrator or the owner of this Team, which is required by the migration.

Recommendations:

Make sure the service account configured in the connection is the Teams Service Administrator or the owner of the Team, and rerun an incremental or "Retry error objects" migration job.

TG-TenantQuotaExceed

Issue:

The object failed in the migration with the following error:

- **TG-TenantQuotaExceed**

Details:

The error indicates that the number of Teams created by the destination connection account exceeds the tenant limit.

Recommendations:

Contact your administrator to increase the limit for the destination connection account to create Teams, or delete destination Teams to reduce the used quota.

TG-NotSupportNickName

Issue:

The Group/Team failed in the migration with the following error:

- **TG-NotSupportNickName**

Details:

The Group/Team cannot be created in the destination since its mailnickname has invalid characters.

Recommendations:

Remove the invalid characters and rerun the migration job.