Microsoft errors fall into two main categories:
- Tenant-related errors, such as batch failures and rate limiting
- Errors related to doing something that is prohibited by Microsoft, such as moving data to an unprovisioned account or creating a path that is more than the Microsoft limit of 400 characters
There are ways to remediate most of these errors, and this article will cover the most common ones.
JobImportant: ID: ### and JobRestart: ID: ###: These errors appear in the event log for your job. CFP moves data to the Azure layer of your Microsoft account, but Microsoft must move the file to your OneDrive or Sharepoint account. Microsoft then sends a response to CFP if the file transfer has completed successfully. If the file transfer fails, Microsoft sends the messages at left back to CFP, and CFP will retry the file. This message is benign except that the Microsoft failures can slow down the job. These are Microsoft errors and not CFP errors.
Remediation: seeing a few of these errors in your jobs is not unusual. The number seen depends somewhat on the size of the affected job, and on how many other jobs are running to the same target. If you consistently see more than ~50 errors in a single job:
- file a support ticket with Microsoft. In addition to following up directly on that ticket, send your tenant ID and the ticket number to email@example.com, as we can sometimes forward the information directly to our contacts at Microsoft.
- select Decoupled SPO Migration Jobs in Advanced Fields > Target Fields. If you restart the job, it will look at batches that are still in progress from the last job. The job will fail until all previous batches have completed, so you are not attempting to re-send batches that are already complete, but haven’t fully moved from Azure to OneDrive/SPO.
Name too long: the affected path contains a stanza (folder or filename) that contains more than 255 characters when converted to a URL.
Remediation: Rename the affected item on the source. Because this item has failed to transfer, renaming the affected item is unlikely to result in duplicate data on the target. However, best practices are to run a simulation to check for these issues ahead of any actual data transfer. See All Adapters (non admin and admin) > Identify Paths, Folder and File Names That Are Too Long in the article Microsoft Adapters: OneDrive and Sharepoint Online Overview for additional information.
Path too long: the affected path is more than 400 characters when converted to the full URL.
Remediation: Rename the affected item on the source. Depending on how you rename the path, this may result in duplicate data. See All Adapters (non admin and admin) > Identify Paths, Folder and File Names That Are Too Long in the article Microsoft Adapters: OneDrive and Sharepoint Online Overview for additional information.
User [username] (email) does not have a provisioned OneDrive: The user may have a OneDrive account, but they don’t have personal space to write data to.
Remediation: Accounts can be bulk provisioned with scripts; see Admin Adapters > Provisioning Users (OneDrive Target Migrations Only) in the article Microsoft Adapters: OneDrive and Sharepoint Online Overview for additional information.
The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator, failed to apply permissions.: You are trying to apply an ACL to a folder that contains more than 100,000 items. See ACL Limits > Number of Items That Have a Given ACL in the article Microsoft Adapters: OneDrive and Sharepoint Online Overview for additional information.