Troubleshoot Migration Managing director issues and errors

  • Article
  • xiii minutes to read

This commodity describes how to resolve bug and errors you may experience when using Migration Manager.

  • Prerequisites and settings
  • Agent error messages
  • Destination site URL issues
  • Common error letters
  • Agent installation failure
  • Agent asunder
  • Job stuck in "Queued" land
  • Task report cannot exist downloaded
  • Migration errors in task reports
  • Google migration error reports contain HTML
  • Mistake codes
  • Geo admins can't access full functionality of Migration Manager
  • Group-inherited SharePoint admins can't access total 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. Regime cloud customers should confirm they have set their configuration correctly.

  • Agent installation prerequisites

  • Required endpoints

  • Government cloud settings

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

Amanuensis error messages

Message Action
Migration agent could not be installed. Close setup and try again. You may exist using an out-of-appointment version of the agent setup file to install the agent. Run into Agent installation failure below for more than information.
Current user does non 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 amanuensis has read permissions to the file share y'all want to migrate.
The source file share does non exist Brand sure the source file share is an existing network file share. Confirm that the Windows business relationship associated with the agent has read permissions to the file share y'all want to migrate.

Destination site URL problems

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

Oftentimes 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 exist created or updated Brand 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 however fails, create the site manually and point the migration tool to this newly created site.
Scan file failure: The folder proper noun is invalid Encounter Invalid file names and file types in OneDrive and SharePoint
Scan file failure: Target path is too long Run into 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.
Browse File Failure: Not enough deejay space to pack the file The disk space available for the migration working binder is too pocket-size for the size of your source file. Enlarge your size of your working folder effort over again.
Packaging failure: Cannot open file Packaging failed due to non-existing source. Check if yous can access the source root folder.
A indistinguishable task has already been created. The CSV file used to do bulk migration cannot have duplicate entries. Remove the duplicate line(s) and try again.
The parent folder was not migrated The parent folder was non migrated, therefore all items under the folder volition fail to migrate. Bank check your parent binder and retry your migration.

Amanuensis installation failure

Issue: 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 heart in the SharePoint admin center, 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 yous desire to install the amanuensis. Follow the instructions to consummate the agent installation.

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

Example:

Migration Manager agent installation failure

Diagnosis / Investigation

If the clientsetup.exe cannot exist opened:

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

If errors occurred during installation procedure:

  • The error message should already include the failure reason, and the appropriate actions to accept if possible.
  • If errors do non suggest deportment 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 awarding, or provide the Administrator username and countersign upon opening the application.

If errors occurred during installation process:

  • For errors with specific stated deportment, take the respective activity and then 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 asunder

Issue: The "state" of the amanuensis gets stuck equally "Disconnected" and never comes back.

Agent disconnected

Diagnosis / Investigation

  • Cheque the network health on the computer on which the agent is installed.
  • If the password of the logged-in Tenant Ambassador account has inverse, or whatever other similar, critical changes applied to the Tenant Admin account that would crave 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 agent.
  • Token expiration can also crusade the agent to disconnect.

Mitigation

  • If there's a network effect, prepare that. The agent should reconnect presently after.
  • If there are disquisitional changes to the Tenant Admin account that require you to re-sign in: Reinstall the amanuensis on all the computers.
  • If neither of these condition applies, start by reinstalling the agent start.

Task stuck in "Queued" status

Upshot 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 at that place are agents installed for this tenant. They should exist listed in the Agents list.
  • Check the land of each amanuensis. They should exist fix to "Enabled".
  • A status of "In use" indicates the amanuensis is already processing some other task. The amanuensis won't exist able to exist assigned more tasks without finishing the electric current 1.
  • If an agent is listed as "Disabled", enable them;
  • If they appear to exist "Disconnected" for a long fourth dimension, check Amanuensis Disconnected.

Mitigation

  • If there are available, enabled agents in the listing, 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.

Chore Written report cannot be downloaded

Outcome The Task report cannot be downloaded from the link on the task details panel.

  • The Download task study link is disabled.
  • The Download task report link displays active, only nothing happens afterwards clicking on it

Task report can't be downloaded

Diagnosis / Investigation

  • The link, "Download chore report", is disabled until the task is finished. Reports are only available after the condition of the task has become "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, most probable there are errors that accept occurred during the migration process which interrupted the uploading of the reports to SharePoint. Nonetheless, they tin be found locally every bit long every bit 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 job's outset time. If the task reports be, they will be in the "Report" folder inside this subfolder.

Or

  • If the task has failed, navigate to the folder %AppData%\Microsoft\SPMigration\Logs, so sort the subfolders past their modified time. Find the subfolder whose modified time is the closest to the task's offset time. The error report will be in this subfolder.

Migration errors in task reports

Effect Migration tasks fail due to diverse reasons and are detailed in the job reports.

Migration manager error

Diagnosis / Investigation

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

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

Mitigation Find the specific fault hither for more information: 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

Cheque the settings on any AntiVirus application installed on the agent car. Add together our two 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 report shows HTML code in written report

Upshot 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 mistake.

Mitigation Run less concurrent transations.

Condition This is a known outcome. ETA not set.

Geo admins not supported

Migration Manager currently doesn't support the Geo admin function for specific scenarios. For file share migrations, these users can't access the scans tab. For deject migrations, these users can't admission 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, get 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 want to assign to the user. If you don't run into the function you're looking for, select Testify all at the lesser 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 tin'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 function.

  1. In the admin center, go to the Users > Active users page.
  2. On the Active users page, select the user whose admin office you want to change. In the flyout pane, under Roles, select Manage roles.
  3. Select the admin part that yous want to assign to the user. If you don't encounter the part you're looking for, select Bear witness all at the lesser of the listing.

Mistake codes

Error Code Recommended action
0x00000000 Unexpected error.
0x01110001 Unknown reason.
0x0111000B Path is also long.
0x0111000F The parent folder was non migrated. Check the failure report to decide the file and and so try once more.
0x01110003 Cannot access source folder.
0x01110009 Cound non think the file metadata.
0x01110010 Invalid characters in the file name. Check written report for files names with <>:"?*/,
0x01110011 The item "created fourth dimension" or "modified fourth dimension" 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 access your local storage.  Restart your migration.
0x02010023 Your source listing template is non supported.  Try another.
0x0201000C Check your credentials and then reenter your username and countersign.
0x02010017 You must be a site collection admin.
0x02060009 1 - The site collection 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 grapheme.
iii - The site collection cannot be created or updated.
0x02060007 one - The site collection cannot be created considering the URL is already in use or an invalid URL.
2 - The site drove cannot be created because the URL contains invalid character.
0x02010018 i - Check your credentials and and so try again.
2 - A problem occurred accessing SharePoint.  Check your credentials and effort again.
3 - A trouble occurred accessing SharePoint.  Bank check your credentials and your network connection and try again.
four - A problem occurred accessing SharePoint.  Check your credentials and your site URL for accuracy and try again.
v - 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 endeavor 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 bundle 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 - Bank check your credentials. Restart your migration.
2 - Bank check your credentials. Restart your migration.
3 - Check your credentials and your network connection. Restart your migration.
iv - Check your credentials and your site URL. Restart your migration.
5 - Check your credentials and the format of your URL. Restart your migration.
6 - Cheque 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 you have permission to access it.
0x02050001 All files and folders in the Migration Manager working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be airtight. Restart your migration.
0x02010002 Check your network condition. If you tin can access the source sites from a browser, then create a back up 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 closed during migration. Restart your migration.
0x02040012 The temporary storage on your local estimator is too low. Migration Manager 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 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't be created because the directory cannot be found. All files and folders in the Migration Managing director 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. Endeavour to access the URL via a browser. If this is a OneDrive account, make sure it has been pre-provisioned before you drift.
0x0207001 You exercise not have admission to the task folder. Check if you 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. Bank check if the dependencies have been included in your migration scope.
0x01510001 Packages failed to upload. If you take customized Azure storage, cheque if you can access the Azure storage and check if y'all 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. Suspension the task and cheque 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. Neglect to look up folder proper noun. The item may be in other list or site in the same site drove. Or the item is in the recycle bin.
0x0131000F Failed to Read the file. File is checked out.