Troubleshoot Migration Director bug and errors

  • Article
  • 13 minutes to read

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

  • Prerequisites and settings
  • Agent error messages
  • Destination site URL issues
  • Common error messages
  • Agent installation failure
  • Agent disconnected
  • Task stuck in "Queued" state
  • Task report cannot be downloaded
  • Migration errors in chore reports
  • Google migration mistake reports contain HTML
  • Mistake codes
  • Geo admins tin't access total functionality of Migration Director
  • Group-inherited SharePoint admins can't admission full functionality of Migration Manager

Check prerequisites and settings

Make sure y'all have met the prerequisites for agent installation, and accept reviewed the required endpoints. Government deject customers should confirm they have fix their configuration correctly.

  • Agent installation prerequisites

  • Required endpoints

  • Government cloud settings

  • Pre-provision OneDrive accounts If y'all are migrating to OneDrive accounts, make sure the accounts are pre-provisioned earlier you migrate. Y'all tin can do this using a script, as shown hither: Pre-provision OneDrive for users in your arrangement.

Agent error messages

Message Activeness
Migration agent could non be installed. Close setup and effort again. Y'all may exist using an out-of-date version of the agent setup file to install the amanuensis. See Agent installation failure beneath for more information.
Electric 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 account associated with the agent has read permissions to the file share you want to migrate.
The source file share does not be Brand certain the source file share is an existing network file share. Confirm that the Windows account associated with the agent has read permissions to the file share you lot desire to migrate.

Destination site URL bug

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

Frequently seen error messages

Message Recommended action
Invalid source folder Confirm the path you entered is correct and follows the proper format

Confirm you have read access to the folder.
The site cannot be created or updated Make certain that yous take permissions to create the site and that the URL is valid

If the site exists, confirm you are the site collection administrator

If information technology yet fails, create the site manually and point the migration tool to this newly created site.
Scan file failure: The folder name is invalid See Invalid file names and file types in OneDrive and SharePoint
Browse file failure: Target path is likewise long See 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 deejay infinite available for the migration working folder is also small for the size of your source file. Enlarge your size of your working folder endeavour over again.
Packaging failure: Cannot open file Packaging failed due to non-existing source. Bank check if you tin 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 indistinguishable line(southward) and attempt over again.
The parent folder was not migrated The parent binder was non migrated, therefore all items under the folder will neglect to drift. Check your parent binder and retry your migration.

Agent installation failure

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

Screen agent installation failure

Diagnosis / Investigation

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

Mitigation

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

Consequence: 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 Ambassador, or provide the Administrator username and countersign upon opening the application. The Administrator business relationship should already be added to the domain.

If errors occurred during installation process:

  • The error message should already include the failure reason, and the advisable actions to have if possible.
  • If errors practice not suggest actions to resolve, the problem could be caused by temporary network failure, or other unknown problems.

Mitigation

If the clientsetup.exe cannot be opened:

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

If errors occurred during installation process:

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

Agent disconnected

Issue: The "state" of the agent gets stuck every bit "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 business relationship has changed, or any other similar, disquisitional changes applied to the Tenant Admin account that would require re-sign in, all of the agents will be disconnected and reinstallation is required on all of them.
  • If the agent failed to auto-upgrade, the version is likely too old. Reinstall the amanuensis.
  • Token expiration tin also cause the agent to disconnect.

Mitigation

  • If in that location's a network issue, fix that. The agent should reconnect soon after.
  • If at that place 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, showtime by reinstalling the agent first.

Task stuck in "Queued" status

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

Task stuck in Queued status

Diagnosis / Investigation

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

Mitigation

  • If there are available, enabled agents in the list, only the tasks oasis't been scheduled for a long time: Create another job that is the same. Sometimes it will fix the trouble.

Chore Written report cannot be downloaded

Issue The Task report cannot be downloaded from the link on the task details console.

  • The Download chore report link is disabled.
  • The Download task report link displays active, merely cipher happens after clicking on information technology

Task report can't be downloaded

Diagnosis / Investigation

  • The link, "Download task study", is disabled until the chore is finished. Reports are only available after the status of the job 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, non-timed-out tasks, nigh likely there are errors that have occurred during the migration process which interrupted the uploading of the reports to SharePoint. Nonetheless, they can exist plant locally every bit long as they be.

Mitigation

On the calculator that completed the task, try to call back 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. Discover the subfolder whose modified fourth dimension is the closest to the task'southward outset fourth dimension. If the task reports exist, they will be in the "Report" folder within this subfolder.

Or

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

Migration errors in job reports

Upshot Migration tasks neglect due to diverse reasons and are detailed in the job reports.

Migration manager error

Diagnosis / Investigation

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

  • If you lot can't download the task reports, delight refer to Task Report Cannot Be Downloaded

Mitigation Notice the specific error here for more than data: Mistake 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 auto. Add our 2 migration applications every bit exceptions and then that the migration traffic won't be interrupted:

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

Google error report shows HTML code in written report

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

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 consequence. ETA not set.

Geo admins non supported

Migration Manager currently doesn't support the Geo admin function for specific scenarios. For file share migrations, these users tin can't access the scans tab. For cloud migrations, these users tin 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, go to the Users > Agile users page.
  2. On the Active users folio, select the user whose admin role you want to change. In the flyout pane, under Roles, select Manage roles.
  3. Select the admin office that you want to assign to the user. If y'all don't see the office you're looking for, select Show all at the bottom of the list.

SharePoint admin roles that were created equally a event of joining an Azure group are not fully supported by Migration Manager. For file share migrations, these users can't access the scans tab. For cloud migrations, these users can't admission 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 eye, go to the Users > Agile users page.
  2. On the Active users page, select the user whose admin office yous want to change. In the flyout pane, under Roles, select Manage roles.
  3. Select the admin part that you want to assign to the user. If you don't see the role yous're looking for, select Show all at the lesser of the list.

Fault codes

Mistake Code Recommended action
0x00000000 Unexpected error.
0x01110001 Unknown reason.
0x0111000B Path is besides long.
0x0111000F The parent folder was not migrated. Check the failure study to make up one's mind the file and then effort once again.
0x01110003 Cannot access source binder.
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 fourth dimension" is not supported.
0x0201000D Check if the list exists or if you tin can 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 Check your credentials and and then reenter your username and password.
0x02010017 Yous must exist a site drove admin.
0x02060009 1 - The site collection cannot be created because the URL is already in utilise or an invalid URL.
2 - The site collection cannot be created because the URL contains invalid character.
3 - The site drove cannot be created or updated.
0x02060007 1 - The site collection 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 - Check your credentials and so effort again.
two - A problem occurred accessing SharePoint.  Cheque your credentials and try again.
3 - A trouble occurred accessing SharePoint.  Check your credentials and your network connexion and effort again.
iv - A problem occurred accessing SharePoint.  Bank check your credentials and your site URL for accuracy and effort once more.
5 - A problem 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 again.  If the problem continues, please create a support instance.
7 - A problem occurred accessing SharePoint.  Cheque your credentials and try 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 - Cheque your credentials. Restart your migration.
2 - Cheque your credentials. Restart your migration.
iii - Bank 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.
six - Check your credentials and restart your migration. If this continues, delight a back up case.
vii - Check your credentials and attempt 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 Manager working binder, %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, and then create a support case.
0x02010010 Make certain the source list and target list accept the same template.
0x0204000D All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist closed during migration. Restart your migration.
0x02040012 The temporary storage on your local calculator is too low. Migration Manager caches the packet on the working folder. Aggrandize your temporary storage and retry.
0x02030003 There are likewise 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 binder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02040009 The packet can't be created because the directory cannot be plant. 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. Try to access the URL via a browser. If this is a OneDrive account, brand certain information technology has been pre-provisioned before you migrate.
0x0207001 You do not have admission to the chore folder. Check if y'all can access %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage.
0x01410010 A failure occurred considering of missing dependencies on list items. Check the FailureSummaryReport.csv for details. Cheque if the dependencies have been included in your migration telescopic.
0x01510001 Packages failed to upload. If yous have customized Azure storage, check if you lot tin can admission the Azure storage and check if y'all tin admission the target site. Effort migrating again.
0x01510001 Failed to Upload the Job to Server: Upload file failed during migration.
0x02070009 Several packages failed to upload. Suspension the task and check your network connection.
0x01710009 A failure occurred due to job end failures; some items failed in the package. 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 Error.
0x01710004 Errors or timeout for server processing the file. Fail to expect up folder proper noun. The item may exist in other list or site in the aforementioned site collection. Or the detail is in the recycle bin.
0x0131000F Failed to Read the file. File is checked out.