Troubleshoot Migration Manager issues and errors

  • Commodity
  • thirteen minutes to read

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

  • Prerequisites and settings
  • Agent error letters
  • Destination site URL bug
  • Common fault messages
  • Agent installation failure
  • Agent disconnected
  • Task stuck in "Queued" state
  • Chore report cannot be downloaded
  • Migration errors in task reports
  • Google migration fault reports contain HTML
  • Error codes
  • Geo admins can't access full functionality of Migration Manager
  • Group-inherited SharePoint admins can't access full functionality of Migration Manager

Bank check prerequisites and settings

Make sure you have met the prerequisites for agent installation, and have reviewed the required endpoints. Authorities cloud customers should confirm they take set up their configuration correctly.

  • Agent installation prerequisites

  • Required endpoints

  • Authorities cloud settings

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

Agent fault messages

Message Action
Migration amanuensis could non exist installed. Shut setup and try again. You may be using an out-of-date version of the agent setup file to install the agent. Meet Agent installation failure below for more data.
Current user does not have access to source file share Make certain 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 y'all want to migrate.
The source file share does not be Make sure the source file share is an existing network file share. Ostend that the Windows account associated with the agent has read permissions to the file share you lot want to migrate.

Destination site URL issues

Bulletin Recommended action
Destination site or web does not exist Confirm the destination site or subsite exists. If OneDrive business relationship, make sure that it has been pre-provisioned.
Failed to check site or web existence. Ostend the destination site or subsite exists.

Frequently seen error messages

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

Ostend you have read admission to the folder.
The site cannot be created or updated Make sure that yous 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 nonetheless fails, create the site manually and point the migration tool to this newly created site.
Browse file failure: The binder name is invalid Come across Invalid file names and file types in OneDrive and SharePoint
Scan file failure: Target path is too long Meet Invalid file names and file types in OneDrive and SharePoint

The entire path, including the file proper name, must contain fewer than 400 characters for OneDrive and SharePoint.
Scan File Failure: Not plenty disk space to pack the file The deejay space available for the migration working folder is besides small for the size of your source file. Overstate your size of your working binder try again.
Packaging failure: Cannot open up file Packaging failed due to non-existing source. Check if yous can access the source root folder.
A duplicate task has already been created. The CSV file used to exercise bulk migration cannot have duplicate entries. Remove the duplicate line(s) and effort again.
The parent folder was not migrated The parent binder was not migrated, therefore all items under the folder will neglect to migrate. Check your parent folder and retry your migration.

Agent installation failure

Consequence: The migration agent fails to install when using an old version of amanuensis setup file to install agent.

Screen agent installation failure

Diagnosis / Investigation

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

Mitigation

  1. Go to the Migration middle in the SharePoint admin center, and sign in with an account 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 y'all want to install the agent. Follow the instructions to complete the agent installation.

Outcome: 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 as Administrator, or provide the Administrator username and password upon opening the application. The Ambassador account should already be added to the domain.

If errors occurred during installation process:

  • The error message should already include the failure reason, and the appropriate actions to take if possible.
  • If errors do non advise actions to resolve, the problem could be acquired by temporary network failure, or other unknown bug.

Mitigation

If the clientsetup.exe cannot exist opened:

  1. Sign in to Windows as Administrator.
  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 actions, take the corresponding action and and then reopen the clientsetup.exe.
  • For other non-specific errors, make sure your Administrator business relationship has been added to the domain. Close the awarding window and and so retry installation.

Agent disconnected

Consequence: The "state" of the amanuensis gets stuck every bit "Disconnected" and never comes back.

Agent disconnected

Diagnosis / Investigation

  • Cheque the network health on the reckoner on which the agent is installed.
  • If the countersign 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 volition be asunder and reinstallation is required on all of them.
  • If the agent failed to machine-upgrade, the version is likely too erstwhile. Reinstall the agent.
  • Token expiration can likewise cause the agent to disconnect.

Mitigation

  • If there's a network issue, set up that. The agent should reconnect soon afterwards.
  • If there are critical 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, first by reinstalling the agent first.

Job 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 sure in that location are agents installed for this tenant. They should exist listed in the Agents listing.
  • Check the land of each agent. They should be set to "Enabled".
  • A status of "In use" indicates the agent is already processing another chore. The agent won't be able to be assigned more tasks without finishing the electric current one.
  • If an agent is listed equally "Disabled", enable them;
  • If they appear to exist "Disconnected" for a long time, check Agent Asunder.

Mitigation

  • If there are available, enabled agents in the list, merely the tasks haven't been scheduled for a long time: Create another task that is the same. Sometimes it will fix the problem.

Job Report cannot be downloaded

Outcome The Chore report cannot exist downloaded from the link on the task details console.

  • The Download task report link is disabled.
  • The Download task study link displays active, only nada happens after 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 just available later the status of the job has go "Complete" or "Failed". Tasks that failed due to time-out will also take a disabled task report link.
  • If no reports tin can be downloaded for finished, non-timed-out tasks, virtually likely there are errors that have occurred during the migration procedure which interrupted the uploading of the reports to SharePoint. Even so, they can be plant locally every bit long as they exist.

Mitigation

On the computer that completed the task, attempt to retrieve 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 fourth dimension is the closest to the task's outset fourth dimension. If the chore reports exist, they will exist in the "Written report" folder 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 fourth dimension is the closest to the task'south start time. The error report will be in this subfolder.

Migration errors in job reports

Effect Migration tasks fail due to various reasons and are detailed in the chore reports.

Migration manager error

Diagnosis / Investigation

  • The failure reasons should already be written in particular to the reports along with suggested solutions.

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

Mitigation Detect the specific error here for more than information: Fault codes.

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

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

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

Google error study shows HTML code in report

Issue Error reports generated for a Google migration will sometimes have HTML lawmaking embedded in the study.

Google error report includes HTML code

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

Mitigation Run less concurrent transations.

Status This is a known issue. ETA not set.

Geo admins not supported

Migration Managing director currently doesn't support the Geo admin role for specific scenarios. For file share migrations, these users tin'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 function.

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

SharePoint admin roles that were created as a result of joining an Azure group are non fully supported by Migration Managing director. For file share migrations, these users tin'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 part.

  1. In the admin center, go to the Users > Active users page.
  2. On the Active users page, select the user whose admin function you want to change. In the flyout pane, nether Roles, select Manage roles.
  3. Select the admin role that you 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 listing.

Error codes

Error Code Recommended activity
0x00000000 Unexpected mistake.
0x01110001 Unknown reason.
0x0111000B Path is too long.
0x0111000F The parent folder was not migrated. Cheque the failure written report to make up one's mind the file and so try again.
0x01110003 Cannot access source folder.
0x01110009 Cound not 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 can admission it in the source site and target site.
0x02050008 Unable to admission your local storage.  Restart your migration.
0x02010023 Your source listing template is not supported.  Try another.
0x0201000C Check your credentials and and so reenter your username and countersign.
0x02010017 Y'all must be a site collection admin.
0x02060009 1 - The site collection cannot be created because the URL is already in apply or an invalid URL.
2 - The site collection cannot exist created because the URL contains invalid grapheme.
3 - The site collection cannot exist created or updated.
0x02060007 1 - The site drove cannot be created because the URL is already in utilise or an invalid URL.
2 - The site collection cannot exist created because the URL contains invalid character.
0x02010018 1 - Cheque your credentials and then try again.
2 - A problem occurred accessing SharePoint.  Bank check your credentials and try over again.
3 - A problem occurred accessing SharePoint.  Cheque your credentials and your network connection and try again.
four - A trouble occurred accessing SharePoint.  Bank check your credentials and your site URL for accurateness and try again.
5 - A trouble occurred accessing SharePoint.  Check your credentials and the format of your URL. Retry.
6 - A problem occurred accessing SharePoint.  Bank check your credentials and try over again.  If the problem continues, delight create a support instance.
7 - 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 Managing director working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist closed. Restart your migration.
0x02030001 i - Bank check your credentials. Restart your migration.
2 - Cheque your credentials. Restart your migration.
3 - Check your credentials and your network connectedness. Restart your migration.
4 - Check your credentials and your site URL. Restart your migration.
v - 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 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 yous have permission to admission it.
0x02050001 All files and folders in the Migration Director working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist closed. Restart your migration.
0x02010002 Cheque your network status. If you lot can access the source sites from a browser, and so create a support example.
0x02010010 Make certain the source listing and target list have the same template.
0x0204000D All files and folders in the Migration Managing director working binder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist closed during migration. Restart your migration.
0x02040012 The temporary storage on your local reckoner is too depression. Migration Manager caches the parcel on the working folder. Expand your temporary storage and retry.
0x02030003 There are too many items with unique permissions. Simplify your permissions list past 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 changed or deleted while uploading. All files and folders in the Migration Managing director working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02040009 The package tin can'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 exist airtight. 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, brand sure it has been pre-provisioned before you migrate.
0x0207001 You do non have access to the task folder. Check if yous tin can access %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 have been included in your migration scope.
0x01510001 Packages failed to upload. If yous have customized Azure storage, cheque if you can access the Azure storage and check if you can access the target site. Try migrating once more.
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: Non 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. Fail to look up folder proper name. The item may exist 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.