Sharepoint Online Migration Manager failed tasks

Question

Sharepoint Online Migration Manager failed tasks

Stefanos Evangelou 116

Hello,

I am running a migration of on-premise file server (Windows Server 2019) to my Sharepoint Online tenant using Sharepoint Online Migration Manager. I have successfully installed the Migration Manager agent on the file server and have configured it with a) global admin user of the M365 tenant and b) full NTFS permissions user on the file server. I performed an initial migration and it was successful. Also I have run subsequent migrations afterwards running the same migration tasks but this time I enabled the filter to only migrate files created after a certain date. This run was also successful. However, after running the migration tasks for a third time after some time, I can now see that the tasks are failing. The "Download Task Report" button is inactive so I cannot see any verbose logging of the error(s).

I have checked against all service limitations (e.g. total number of files, etc) and everything is covered except for requirement for Solid state disk: 150-GB free space (as per https://learn.microsoft.com/en-us/sharepointmigration/mm-setup-clients).

Do you have any other ideas on why this could be happening and how to get any traces/logs when the task report cannot be retrieved (greyed out option)?

Accepted answer

0 additional answers

Your answer

Answer 1

ChelseaWu-MSFT 6,341

Do you see any error message on the Details page of the task? Is there any “file scanned with issues” listed?

The local Migration Manager logs are stored under this location: C:\Users\<User>\AppData\Roaming\Microsoft\SPMigration\Logs
And the logs for individual migration tasks: C:\Users\<User>\AppData\Roaming\Microsoft\SPMigration\Logs\Migration\MigrationTool\<tenant>.onmicrosoft.com

You can check these two locations for logs on the failed task or the Migration Manager itself for potential error message.
Here is a document you can check for possible error messages or error codes during troubleshooting: Troubleshoot Migration Manager issues and errors.

In addition, make sure you do not contain too many characters in one filename. Referring to this document: Frequently Asked Questions: Migration Manager:
The limit to the number of path characters is 255 characters.

However, during migration the file path can be up to 32,767 characters in length. After it is migrated into SPO, the path is limited to 400 characters.

If an Answer is helpful, please click "Accept Answer" and upvote it.
**Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. **

ChelseaWu-MSFT 6,341 Reputation points

2020-12-07T00:20:03.863+00:00

Hi @Stefanos Evangelou , do you have any progress on this thread? Please feel free to let us know if you need further assistance.
Stefanos Evangelou 116 Reputation points

2020-12-09T09:07:31.42+00:00

Hello,

I am currently running the migration tasks again and will check all the recommended actions and log paths and I will revert with findings.
ChelseaWu-MSFT 6,341 Reputation points

2020-12-09T23:32:08.703+00:00

Thanks for the update. Looking forward to hearing from you soon.
Stefanos Evangelou 116 Reputation points

2020-12-16T08:35:48.737+00:00

After checking the Migration Manager logs on the machine where the agent is running, the following is the clear indication of the root cause:

[2020/12/10 22:21:00.546][Info][16]MigrationTask '8a039a21-16e8-4a19-94d6-5a73a13ffe50' Reached its Status 'PAUSE'
[2020/12/10 22:21:00.546][Info][16][MigReport] Temporary storage on your local computer is too low.
System.AggregateException: One or more errors occurred. ---> System.IO.IOException: There is not enough space on the disk.
TaskID Message PendingAction ExceptionId
4a222df9-be18-492c-9d58-8ce1a3798cdf Failed to access local storage. ACTION_STOP 0x02050008

Now question is how can I increase the temporary storage seen by the Migration Manager agent? The local disk of the machine where the agent is running has ~150 GB free space, as per the requirements at: https://learn.microsoft.com/en-us/sharepointmigration/mm-setup-clients#prerequisites.

Any ideas?
ChelseaWu-MSFT 6,341 Reputation points

2020-12-16T09:28:19.283+00:00

According to this document, Migration Manager caches the package on the working folder during this process, where you will need more space for the task to carry on.

The path of the working folder for Migration Manager is: %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, the free size of which should be greater than the size of your contents to be uploaded to SharePoint Online.

Currently, it is not supported to change the location of the working folder. Make sure you have enough free space in this folder.
ChelseaWu-MSFT 6,341 Reputation points

2020-12-16T09:29:20.087+00:00

Or you can use mklink to point a junction to another section on your local disk, or an external HDD, as is referred to another similar post here: Temporary storage on your local computer is too low. (ErrorCode: 0x02040012).

I have not tested with this method though, you can take it into consideration if you have trouble expanding the storage of the original working folder.
Stefanos Evangelou 116 Reputation points

2020-12-16T10:28:55.43+00:00

I performed a cleanup of this folder which was ~7 GB in size. It is now ~100 MB. I will perform the migration tasks again and revert.
ChelseaWu-MSFT 6,341 Reputation points

2020-12-17T01:23:24.783+00:00

@Stefanos Evangelou , feel free to let us know if you need further assistance.
Stefanos Evangelou 116 Reputation points

2020-12-17T09:38:13.083+00:00

My migration tasks are still in Queued status for more than 24h now and I have confirmed that the agent is active/enabled. I will send you an update once the migration tasks have been executed after the latest change of free space in the app data folder.
Stefanos Evangelou 116 Reputation points

2020-12-18T23:20:55.707+00:00

I had to re-install the Migration Manager agent and afterwards delete all tasks which were stuck in "Queued" state. Then I re-created the tasks and this time they are all successful. Case can be closed. Thank you for your support.

Share via

Sharepoint Online Migration Manager failed tasks

0 additional answers

Your answer