Troubleshoot Migration Director bug and errors

  • Article
  • 13 minutes to read

This article describes how to resolve issues and errors y'all may experience when using Migration Director.

  • Prerequisites and settings
  • Agent mistake letters
  • Destination site URL bug
  • Mutual error letters
  • Amanuensis installation failure
  • Agent disconnected
  • Task stuck in "Queued" state
  • Chore study cannot be downloaded
  • Migration errors in task reports
  • Google migration mistake reports contain HTML
  • Error codes
  • Geo admins can't admission full functionality of Migration Managing director
  • Group-inherited SharePoint admins can't access total functionality of Migration Manager)

Cheque prerequisites and settings

Make certain y'all have met the prerequisites for agent installation, and have reviewed the required endpoints. Government cloud customers should confirm they have set up their configuration correctly.

  • Amanuensis installation prerequisites

  • Required endpoints

  • Government deject settings

  • Pre-provision OneDrive accounts If you are migrating to OneDrive accounts, make sure the accounts are pre-provisioned before you drift. You can practice this using a script, every bit shown here: Pre-provision OneDrive for users in your organization.

Amanuensis error messages

Message Activeness
Migration agent could not be installed. Close setup and try again. You may exist using an out-of-date version of the agent setup file to install the agent. Encounter Agent installation failure below for more data.
Electric current user does not have access to source file share Make sure the source file share is a network file share. Verify that the Windows account associated with the agent has read permissions to the file share you want to migrate.
The source file share does non exist Make sure the source file share is an existing network file share. Ostend that the Windows account associated with the amanuensis has read permissions to the file share you want to drift.

Destination site URL issues

Message Recommended action
Destination site or spider web does not be Confirm the destination site or subsite exists. If OneDrive account, brand sure that it has been pre-provisioned.
Failed to check site or web existence. Confirm the destination site or subsite exists.

Frequently seen error messages

Bulletin Recommended activeness
Invalid source folder Ostend the path you lot entered is right and follows the proper format

Confirm yous have 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 you are the site collection administrator

If it even so fails, create the site manually and indicate the migration tool to this newly created site.
Browse file failure: The folder name is invalid See Invalid file names and file types in OneDrive and SharePoint
Scan file failure: Target path is likewise long Run across Invalid file names and file types in OneDrive and SharePoint

The entire path, including the file name, must incorporate fewer than 400 characters for OneDrive and SharePoint.
Scan File Failure: Non enough disk space to pack the file The disk space available for the migration working binder is too modest for the size of your source file. Overstate your size of your working folder try once again.
Packaging failure: Cannot open file Packaging failed due to non-existing source. Bank check if yous tin can access the source root folder.
A indistinguishable task has already been created. The CSV file used to do bulk migration cannot accept duplicate entries. Remove the indistinguishable line(south) and try again.
The parent folder was not migrated The parent folder was not migrated, therefore all items under the folder will fail to drift. Check your parent folder and retry your migration.

Agent installation failure

Issue: The migration agent fails to install when using an one-time version of amanuensis setup file to install agent.

Screen agent installation failure

Diagnosis / Investigation

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

Mitigation

  1. Go to the Migration center in the SharePoint admin heart, and sign in with an account that has admin permissions for your system.
  2. Select Download amanuensis setup file.
  3. Run the clientsetup.exe file on the computer or VM where y'all want to install the agent. Follow the instructions to complete the agent installation.

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

Example:

Migration Manager agent installation failure

Diagnosis / Investigation

If the clientsetup.exe cannot be opened:

  • Sign in to Windows every bit Administrator, or provide the Ambassador username and countersign upon opening the application. The Ambassador business relationship should already exist added to the domain.

If errors occurred during installation process:

  • The error message should already include the failure reason, and the appropriate actions to have if possible.
  • If errors exercise 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 Ambassador.
  2. Reopen the clientsetup.exe application, or provide the Administrator username and password upon opening the application.

If errors occurred during installation process:

  • For errors with specific stated deportment, accept the corresponding action and and then reopen the clientsetup.exe.
  • For other non-specific errors, brand sure your Ambassador account has been added to the domain. Close the awarding window and then retry installation.

Agent disconnected

Issue: The "land" of the agent gets stuck as "Disconnected" and never comes back.

Agent disconnected

Diagnosis / Investigation

  • Check the network health on the computer on which the agent is installed.
  • If the password of the logged-in Tenant Administrator account has changed, or any other similar, disquisitional changes practical to the Tenant Admin business relationship that would require re-sign in, all of the agents will exist disconnected and reinstallation is required on all of them.
  • If the amanuensis failed to auto-upgrade, the version is likely besides old. Reinstall the agent.
  • Token expiration can also cause the agent to disconnect.

Mitigation

  • If at that place's a network outcome, fix that. The agent should reconnect soon afterward.
  • If there are disquisitional changes to the Tenant Admin account that require you to re-sign in: Reinstall the agent on all the computers.
  • If neither of these condition applies, start by reinstalling the agent first.

Task stuck in "Queued" status

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

Task stuck in Queued status

Diagnosis / Investigation

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

Mitigation

  • If there are bachelor, enabled agents in the list, but the tasks haven't been scheduled for a long time: Create another task that is the aforementioned. Sometimes information technology will fix the problem.

Job Report cannot exist downloaded

Issue The Job report cannot exist downloaded from the link on the job details panel.

  • The Download task report link is disabled.
  • The Download task report link displays active, simply zilch happens subsequently clicking on it

Task report can't be downloaded

Diagnosis / Investigation

  • The link, "Download task report", is disabled until the task is finished. Reports are only available after the status of the task has become "Complete" or "Failed". Tasks that failed due to time-out will too have a disabled job report link.
  • If no reports can exist downloaded for finished, non-timed-out tasks, most probable there are errors that take occurred during the migration process which interrupted the uploading of the reports to SharePoint. However, they tin be found locally as long as they exist.

Mitigation

On the computer that completed the task, 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'southward start time. If the task reports exist, they will be in the "Report" binder within this subfolder.

Or

  • If the task has failed, navigate to the folder %AppData%\Microsoft\SPMigration\Logs, then sort the subfolders past their modified time. Find the subfolder whose modified time is the closest to the job's start time. The error 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.

Migration manager error

Diagnosis / Investigation

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

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

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

If you receive an error similar to this: SUBMITTING FAILURE Failed to Submit the Job to Server:Unknown failed reason when submitting a job. 0x01610002

Check the settings on any AntiVirus application installed on the agent machine. Add our 2 migration applications as exceptions so that the migration traffic won't be interrupted:

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

Google mistake study shows HTML code in study

Result Error reports generated for a Google migration will sometimes take HTML code embedded in the report.

Google error report includes HTML code

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 not supported

Migration Manager currently doesn't support the Geo admin role for specific scenarios. For file share migrations, these users can't access the scans tab. For deject migrations, these users tin can't admission neither the scans nor the migrations tab.

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

  1. In the admin middle, go to the Users > Active users page.
  2. On the Active users page, select the user whose admin role you want to change. In the flyout pane, under Roles, select Manage roles.
  3. Select the admin part that you lot want to assign to the user. If you don't meet the office you're looking for, select Prove all at the bottom of the list.

SharePoint admin roles that were created as a result of joining an Azure group are not fully supported past Migration Manager. For file share migrations, these users can't access the scans tab. For cloud migrations, these users tin 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, get to the Users > Active users page.
  2. On the Active users page, select the user whose admin role you want to change. In the flyout pane, under Roles, select Manage roles.
  3. Select the admin role that y'all desire to assign to the user. If you don't run across the function yous're looking for, select Show all at the bottom of the list.

Mistake codes

Mistake Code Recommended action
0x00000000 Unexpected error.
0x01110001 Unknown reason.
0x0111000B Path is too long.
0x0111000F The parent folder was not migrated. Check the failure report to determine the file and then endeavor once more.
0x01110003 Cannot access source folder.
0x01110009 Cound non retrieve the file metadata.
0x01110010 Invalid characters in the file name. Check report for files names with <>:"?*/,
0x01110011 The item "created time" or "modified time" is not supported.
0x0201000D 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 another.
0x0201000C Bank check your credentials and and so reenter your username and password.
0x02010017 You must be a site collection admin.
0x02060009 1 - The site drove cannot be created considering the URL is already in apply or an invalid URL.
ii - The site collection cannot be created because the URL contains invalid graphic symbol.
3 - The site collection cannot exist created or updated.
0x02060007 1 - The site drove cannot be created because the URL is already in apply or an invalid URL.
2 - The site drove cannot be created because the URL contains invalid grapheme.
0x02010018 1 - Cheque your credentials and then endeavor again.
two - A problem occurred accessing SharePoint.  Check your credentials and try again.
three - A problem occurred accessing SharePoint.  Cheque your credentials and your network connection and attempt again.
4 - A problem occurred accessing SharePoint.  Check your credentials and your site URL for accuracy and try again.
5 - A problem occurred accessing SharePoint.  Check your credentials and the format of your URL. Retry.
6 - A problem occurred accessing SharePoint.  Check your credentials and effort once again.  If the trouble continues, delight create a support case.
vii - A trouble occurred accessing SharePoint.  Check your credentials and attempt opening your site in a browser.
0x0204000A Cannot create package file. All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02030001 1 - Check your credentials. Restart your migration.
two - Cheque your credentials. Restart your migration.
iii - Check your credentials and your network connection. Restart your migration.
iv - Bank 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, please a support case.
seven - 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 information technology.
0x02050001 All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist closed. Restart your migration.
0x02010002 Check your network status. If you tin admission the source sites from a browser, then create a support example.
0x02010010 Make sure the source list and target list have the same template.
0x0204000D All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be airtight during migration. Restart your migration.
0x02040012 The temporary storage on your local computer is too depression. Migration Director caches the packet on the working folder. Expand your temporary storage and retry.
0x02030003 There 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 folder was touched or modified during the migration. Retry your migration.
0x02080001 The file in the package has been inverse or deleted while uploading. All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist closed. Restart your migration.
0x02040009 The bundle can't exist created considering the directory cannot be constitute. 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 Cheque 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. Try to access the URL via a browser. If this is a OneDrive account, make certain it has been pre-provisioned before you lot migrate.
0x0207001 Yous practice not have access to the task folder. Check if yous tin can admission %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage.
0x01410010 A failure occurred because of missing dependencies on listing items. Check the FailureSummaryReport.csv for details. Check if the dependencies have been included in your migration telescopic.
0x01510001 Packages failed to upload. If you have customized Azure storage, check if you can access the Azure storage and check if y'all tin can access the target site. Try migrating again.
0x01510001 Failed to Upload the Job to Server: Upload file failed during migration.
0x02070009 Several packages failed to upload. Intermission the task and check your network connexion.
0x01710009 A failure occurred due to job cease failures; some items failed in the package. Restart migration.
0x01710009 Errors or timeout for Server Processing the file: Not all the items in the packet have been migrated.
0x01610001 The Azure container is expired. Retry migration job.
0x01710006 Errors or timeout for server processing the file: Chore Fatal Error.
0x01710004 Errors or timeout for server processing the file. Fail to look up binder proper name. The detail may be in other list or site in the same site collection. Or the detail is in the recycle bin.
0x0131000F Failed to Read the file. File is checked out.