Home > OneDrive Related Codes
Export to PDFIssue:
The content type failed in the migration with the following error:
Details:
The error occurs when the source data meets all the following conditions:
The source OneDrive site contains some non-default content types since you have activated some site collection features for the source OneDrive site.
You selected the Only the default Documents library option as the migration scope in the migration policy.
The source non-default content types do not exist in the destination since the site collection features related to these content types are not activated in the destination.
Recommendations:
Check if the source non-default content types are necessary.
If they are not necessary, we recommend that you delete these content types to avoid this issue for later migration jobs.
If they are necessary, choose one of the following options to resolve this issue:
Activate site collection features related to the source non-default content types in the destination and run a "Retry error objects" migration job.
Select the All containers and content in OneDrive option as the migration scope in the migration policy. Then, run a full migration job.
Issue:
The OneDrive site failed with the following error:
Details:
The destination OneDrive site does not exist, and cannot be created in the destination during the migration. It is because the destination is a multi-geo tenant and Fly does not support creating OneDrive sites in multi-geo tenants.
Recommendations:
Here are two options to resolve this issue:
Before the migration job, we recommend that you pre-provision all OneDrive sites using PowerShell: Pre-provision OneDrive for users in your organization.
Make sure users of the destination OneDrive sites to be migrated to log in to OneDrive to initiate the site collection creation.
Issue:
The migration job failed with the following error:
Details:
The error occurs when the destination OneDrive site does not exist and the creation of the OneDrive site has not been completed in 5 minutes. It may be caused by throttling issues or too many requests to API simultaneously.
Recommendations:
Before the migration job, we recommend that you pre-provision all destination OneDrive sites using PowerShell: Pre-provision OneDrive for users in your organization. An alternative approach is for each user to log into OneDrive to initiate the site collection creation.
Issue:
The object failed in the migration with the following error:
Details:
The parent object of this object failed in the migration.
Recommendations:
Check the error details of the parent object in the comment of the Migration errors section by navigating to Projects > Project mappings > View migration report > Migration error tab in Fly. Resolve the errors according to the details, and rerun the migration job.
Issue:
The folder failed in the migration with the following error:
Details:
A shortcut folder exists in the destination, whose URL is the same as the source folder.
Recommendations:
Rename the destination shortcut folder or move the destination shortcut folder to another location, and rerun the migration job.
Issue:
The object failed in the migration with the following error:
Details:
The error may occur when the relative URL of the object is used by a destination subsite or folder. In this case, the object cannot be created in the destination.
Recommendations:
Check if the relative URL of the object is used by a destination subsite or folder.
If the URL is used by a destination subsite or folder, delete the destination subsite or folder and run an incremental or "Retry error objects" migration job to resolve this issue.
If the URL is not used by a destination subsite or folder, contact Support and provide the migration mapping information and job ID to analyze the error.
Issue:
The subsite failed in the migration with the following error:
Details:
Subsites cannot be created in OneDrive sites due to API limitations.
Issue:
The migration of the site collection failed with the following error:
Details:
Your request has been throttled by Microsoft 365 due to frequent requests.
Recommendations:
When throttling occurs in Microsoft 365, it may take minutes or hours to ease up the throttling. We recommend that you wait a bit before you rerun the migration job.