What Does This Meanthe Requested Download Exceeds Your Download Limit Please Try Again Later

Skip to main content

Troubleshoot Migration Managing director issues and errors

• Article
• 02/eighteen/2022
• 13 minutes to read

Is this folio helpful?

Feedback will be sent to Microsoft: Past pressing the submit push, your feedback will be used to improve Microsoft products and services. Privacy policy.

In this article

This article describes how to resolve issues and errors you may experience when using Migration Manager.

• Prerequisites and settings
• Agent error letters
• Destination site URL issues
• Mutual fault messages
• Amanuensis installation failure
• Agent disconnected
• Job stuck in "Queued" state
• Task report cannot exist downloaded
• Migration errors in chore reports
• Google migration error reports contain HTML
• Error codes
• Geo admins tin can't admission full functionality of Migration Manager
• Grouping-inherited SharePoint admins can't admission full functionality of Migration Manager)

Check prerequisites and settings

Make sure you take met the prerequisites for agent installation, and have reviewed the required endpoints. Regime cloud customers should ostend they have fix their configuration correctly.

• Agent installation prerequisites

• Required endpoints

• Government deject settings

• Pre-provision OneDrive accounts If you are migrating to OneDrive accounts, make certain the accounts are pre-provisioned before you migrate. You tin do this using a script, as shown here: Pre-provision OneDrive for users in your system.

Agent fault messages

Message	Action
Migration amanuensis could not exist installed. Close setup and try again.	You may be using an out-of-date version of the amanuensis setup file to install the agent. See Agent installation failure below for more than information.
Current user does not have admission to source file share	Make sure the source file share is a network file share. Verify that the Windows business relationship associated with the agent has read permissions to the file share you desire to migrate.
The source file share does non be	Brand certain the source file share is an existing network file share. Confirm that the Windows account associated with the amanuensis has read permissions to the file share you desire to migrate.

Destination site URL issues

Bulletin	Recommended action
Destination site or web does non exist	Confirm the destination site or subsite exists. If OneDrive account, brand sure that information technology has been pre-provisioned.
Failed to check site or web existence.	Ostend the destination site or subsite exists.

Oft seen error messages

Bulletin	Recommended action
Invalid source folder	Confirm the path you entered is right and follows the proper format Confirm you accept read access to the folder.
The site cannot be created or updated	Make sure that you have permissions to create the site and that the URL is valid If the site exists, confirm y'all are the site collection administrator If it still fails, create the site manually and signal the migration tool to this newly created site.
Scan file failure: The folder proper name is invalid	See Invalid file names and file types in OneDrive and SharePoint
Browse file failure: Target path is too long	Run across Invalid file names and file types in OneDrive and SharePoint The entire path, including the file name, must comprise fewer than 400 characters for OneDrive and SharePoint.
Scan File Failure: Not enough disk space to pack the file	The disk space available for the migration working binder is also pocket-size for the size of your source file. Enlarge your size of your working folder try once again.
Packaging failure: Cannot open file	Packaging failed due to non-existing source. Bank check if you tin can access the source root folder.
A duplicate task has already been created.	The CSV file used to do bulk migration cannot have duplicate entries. Remove the duplicate line(s) and attempt again.
The parent folder was not migrated	The parent binder was not migrated, therefore all items nether the folder will neglect to migrate. Check your parent binder and retry your migration.

Agent installation failure

Issue: The migration agent fails to install when using an sometime version of agent setup file to install agent.

Diagnosis / Investigation

The problem could exist caused by an outdated clientsetup.exe file.

Mitigation

1. Become to the Migration middle in the SharePoint admin center, and sign in with an business relationship that has admin permissions for your organisation.
2. Select Download agent setup file.
3. Run the clientsetup.exe file on the computer or VM where you desire to install the agent. Follow the instructions to consummate the agent installation.

Issue: The migration agent doesn't install successfully, or the clientsetup.exe cannot be opened.

Example:

Diagnosis / Investigation

If the clientsetup.exe cannot be opened:

• Sign in to Windows as Administrator, or provide the Administrator username and password upon opening the application. The Administrator account should already exist added to the domain.

If errors occurred during installation process:

• The error bulletin should already include the failure reason, and the appropriate actions to accept if possible.
• If errors do non suggest actions to resolve, the problem could be caused by temporary network failure, or other unknown issues.

Mitigation

If the clientsetup.exe cannot be opened:

1. Sign in to Windows as Administrator.
2. Reopen the clientsetup.exe application, or provide the Ambassador username and password upon opening the application.

If errors occurred during installation process:

• For errors with specific stated actions, have the corresponding action and and so reopen the clientsetup.exe.
• For other non-specific errors, make sure your Administrator account has been added to the domain. Close the application window and then retry installation.

Agent disconnected

Issue: The "country" of the agent gets stuck every bit "Asunder" and never comes back.

Diagnosis / Investigation

• Bank check the network wellness on the computer on which the agent is installed.
• If the password of the logged-in Tenant Administrator account has inverse, or any other similar, critical changes applied to the Tenant Admin account that would require re-sign in, all of the agents will be asunder and reinstallation is required on all of them.
• If the agent failed to machine-upgrade, the version is probable also onetime. Reinstall the agent.
• Token expiration can likewise crusade the agent to disconnect.

Mitigation

• If there's a network issue, fix that. The agent should reconnect soon subsequently.
• If at that place are disquisitional changes to the Tenant Admin business relationship that crave you to re-sign in: Reinstall the agent on all the computers.
• If neither of these status applies, start by reinstalling the agent first.

Task stuck in "Queued" status

Issue The status of a job stays at "Queued" and never gets scheduled on an amanuensis to run.

Diagnosis / Investigation

• Brand sure there are agents installed for this tenant. They should exist listed in the Agents list.
• Check the country of each amanuensis. They should exist set to "Enabled".
• A status of "In utilize" indicates the amanuensis is already processing another task. The agent won't be able to exist assigned more than tasks without finishing the current one.
• If an agent is listed as "Disabled", enable them;
• If they appear to be "Asunder" for a long time, check Amanuensis Disconnected.

Mitigation

• If there are available, enabled agents in the list, but the tasks haven't been scheduled for a long fourth dimension: Create another job that is the aforementioned. Sometimes it will fix the problem.

Task Report cannot be downloaded

Issue The Task report cannot be downloaded from the link on the job details panel.

• The Download chore report link is disabled.
• The Download task report link displays active, but nothing happens later on clicking on information technology

Diagnosis / Investigation

• The link, "Download task report", is disabled until the task is finished. Reports are simply available after the status of the task has become "Complete" or "Failed". Tasks that failed due to time-out will also have a disabled task report link.
• If no reports can be downloaded for finished, not-timed-out tasks, most likely in that location are errors that have occurred during the migration procedure which interrupted the uploading of the reports to SharePoint. Even so, they can exist found locally as long every bit they be.

Mitigation

On the computer that completed the chore, try to call up the reports.

• In folder %AppData%\Microsoft\SPMigration\Logs\Migration\MigrationTool[tenant_site], or < Your-Customized-Working-Folder >\Migration\MigrationTool[tenant_site], sort the subfolders by their modified time. Find the subfolder whose modified time is the closest to the task's starting time time. If the job reports exist, they will be in the "Report" folder within this subfolder.

Or

• If the job has failed, navigate to the folder %AppData%\Microsoft\SPMigration\Logs, then sort the subfolders by their modified fourth dimension. Find the subfolder whose modified time is the closest to the task's first fourth dimension. The mistake report will be in this subfolder.

Migration errors in task reports

Issue Migration tasks fail due to various reasons and are detailed in the task reports.

Diagnosis / Investigation

• The failure reasons should already exist written in detail to the reports forth with suggested solutions.

• If you can't download the chore reports, please refer to Task Report Cannot Be Downloaded

Mitigation Find the specific error hither for more than information: Error codes.

If you receive an mistake like to this: SUBMITTING FAILURE Failed to Submit the Job to Server:Unknown failed reason when submitting a task. 0x01610002

Check the settings on whatsoever AntiVirus awarding installed on the amanuensis auto. Add our two migration applications every bit exceptions and so that the migration traffic won't be interrupted:

• microsoft.sharepoint.migration.clientservice.exe
• microsoft.sharepoint.migration.mthost.exe

Google error report shows HTML lawmaking in report

Issue Fault reports generated for a Google migration will sometimes have HTML code embedded in the report.

Details The Google APIs are returning HTML errors that are being included in the generated reports. This may happen when there is a Google server load error.

Mitigation Run less concurrent transations.

Status This is a known issue. ETA non set.

Geo admins non supported

Migration Managing director currently doesn't back up the Geo admin part for specific scenarios. For file share migrations, these users tin can't access the scans tab. For cloud migrations, these users can't access neither the scans nor the migrations tab.

Workaround. Assign the Geo user either a SharePoint admin or Global admin role.

1. In the admin center, become to the Users > Active users folio.
2. On the Active users page, select the user whose admin role yous desire to change. In the flyout pane, under Roles, select Manage roles.
3. Select the admin role that you lot want to assign to the user. If you don't see the role you're looking for, select Bear witness all at the bottom of the list.

SharePoint admin roles that were created as a upshot of joining an Azure group are not fully supported by Migration Director. For file share migrations, these users can't access the scans tab. For cloud migrations, these users can't access neither the scans nor the migrations tab.

Workaround. Until this is resolved, assigned the user either a SharePoint admin or Global admin role.

1. In the admin center, go to the Users > Active users folio.
2. On the Active users page, select the user whose admin role you desire to change. In the flyout pane, under Roles, select Manage roles.
3. Select the admin role that y'all want to assign to the user. If you don't come across the part you're looking for, select Show all at the bottom of the list.

Error codes

Error Code	Recommended action
0x00000000	Unexpected fault.
0x01110001	Unknown reason.
0x0111000B	Path is too long.
0x0111000F	The parent folder was not migrated. Check the failure report to determine the file and so attempt once again.
0x01110003	Cannot admission source folder.
0x01110009	Cound not remember the file metadata.
0x01110010	Invalid characters in the file name. Bank check study for files names with <>:"?*/,
0x01110011	The item "created time" or "modified fourth dimension" is not supported.
0x0201000D	Bank check if the list exists or if you tin access it in the source site and target site.
0x02050008	Unable to access your local storage.  Restart your migration.
0x02010023	Your source list template is not supported.  Try some other.
0x0201000C	Bank check your credentials and then reenter your username and countersign.
0x02010017	You must exist a site collection admin.
0x02060009	1 - The site drove cannot be created considering the URL is already in use or an invalid URL.
	2 - The site collection cannot be created because the URL contains invalid character.
	3 - The site collection cannot exist created or updated.
0x02060007	ane - The site collection cannot be created considering the URL is already in apply or an invalid URL.
	2 - The site drove cannot be created because the URL contains invalid graphic symbol.
0x02010018	1 - Check your credentials and and so try again.
	2 - A problem occurred accessing SharePoint.  Bank check your credentials and try once more.
	3 - A trouble occurred accessing SharePoint.  Check your credentials and your network connection and effort again.
	iv - A problem occurred accessing SharePoint.  Check your credentials and your site URL for accuracy and try again.
	5 - A problem occurred accessing SharePoint.  Bank check your credentials and the format of your URL. Retry.
	6 - A problem occurred accessing SharePoint.  Check your credentials and attempt once more.  If the problem continues, delight create a support example.
	7 - A problem occurred accessing SharePoint.  Check your credentials and try opening your site in a browser.
0x0204000A	Cannot create parcel file. All files and folders in the Migration Manager working binder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02030001	i - Bank check your credentials. Restart your migration.
	ii - Check your credentials. Restart your migration.
	3 - Check your credentials and your network connection. Restart your migration.
	4 - Check your credentials and your site URL. Restart your migration.
	5 - Check your credentials and the format of your URL. Restart your migration.
	6 - Check your credentials and restart your migration. If this continues, delight a back up instance.
	7 - Bank check your credentials and try opening your site in a browser. Restart your migration.
0x02010008	Confirm the path and format of the user-mapping file and that you have permission to access it.
0x02050001	All files and folders in the Migration Managing director working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02010002	Check your network status. If you can access the source sites from a browser, then create a support case.
0x02010010	Make certain the source list and target listing have the same template.
0x0204000D	All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed during migration. Restart your migration.
0x02040012	The temporary storage on your local computer is also low. Migration Director caches the package on the working folder. Expand your temporary storage and retry.
0x02030003	At that place are too many items with unique permissions. Simplify your permissions list by reducing the number of unique permissions. aRetry your migration.
0x02050001	Local storage file is corrupted. The working binder was touched or modified during the migration. Retry your migration.
0x02080001	The file in the package has been changed or deleted while uploading. All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02040009	The package tin't be created because the directory cannot be found. All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02010020	Disable migrating version history in Migration Manager settings or enable versioning in SPO.
0x0201000E	Check if the global setting has filtered out special characters in the target path or if the path has unsupported characters.
0X0201000F	Invalid site URL. Check if the site URL is valid. Endeavor to access the URL via a browser. If this is a OneDrive account, make certain it has been pre-provisioned before yous migrate.
0x0207001	You practice not accept access to the job binder. Check if you tin can admission %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage.
0x01410010	A failure occurred because of missing dependencies on list items. Check the FailureSummaryReport.csv for details. Check if the dependencies accept been included in your migration scope.
0x01510001	Packages failed to upload. If you have customized Azure storage, check if yous can admission the Azure storage and check if you can access the target site. Endeavor migrating again.
0x01510001	Failed to Upload the Job to Server: Upload file failed during migration.
0x02070009	Several packages failed to upload. Pause the task and check your network connection.
0x01710009	A failure occurred due to job end failures; some items failed in the packet. Restart migration.
0x01710009	Errors or timeout for Server Processing the file: Not all the items in the package have been migrated.
0x01610001	The Azure container is expired. Retry migration task.
0x01710006	Errors or timeout for server processing the file: Job Fatal Mistake.
0x01710004	Errors or timeout for server processing the file. Neglect to look up folder proper name. The item may exist in other list or site in the same site collection. Or the item is in the recycle bin.
0x0131000F	Failed to Read the file. File is checked out.

Feedback

Submit and view feedback for

michaelsbeasto.blogspot.com

Source: https://docs.microsoft.com/en-us/sharepointmigration/mm-troubleshoot