internal data error possibly because of failure to start the upload

Skip to main content

Troubleshoot Migration Director issues and errors

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

Is this page helpful?

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

In this article

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

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

Check prerequisites and settings

Brand sure you take met the prerequisites for agent installation, and take reviewed the required endpoints. Government deject customers should confirm they accept 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. Y'all can do this using a script, as shown here: Pre-provision OneDrive for users in your organisation.

Amanuensis fault messages

Bulletin	Activity
Migration agent could not exist installed. Close setup and effort again.	You may be using an out-of-date version of the agent 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 account associated with the agent has read permissions to the file share you want to migrate.
The source file share does not 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 migrate.

Destination site URL issues

Bulletin	Recommended action
Destination site or spider web does not exist	Confirm the destination site or subsite exists. If OneDrive account, make sure that it has been pre-provisioned.
Failed to check site or spider 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	Brand sure that you have permissions to create the site and that the URL is valid If the site exists, ostend yous are the site drove administrator If it still fails, create the site manually and point 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 too long	Encounter Invalid file names and file types in OneDrive and SharePoint The entire path, including the file name, must contain fewer than 400 characters for OneDrive and SharePoint.
Scan File Failure: Not enough disk infinite to pack the file	The deejay infinite available for the migration working binder is too small for the size of your source file. Enlarge your size of your working folder try once again.
Packaging failure: Cannot open up file	Packaging failed due to non-existing source. Check if you tin admission the source root folder.
A duplicate task has already been created.	The CSV file used to do majority migration cannot have duplicate entries. Remove the duplicate line(s) and try over again.
The parent folder was not migrated	The parent binder was not migrated, therefore all items under the binder volition fail to migrate. Cheque your parent folder and retry your migration.

Agent installation failure

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

Diagnosis / Investigation

The problem could exist caused by 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 calculator or VM where you want to install the agent. Follow the instructions to complete 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 every bit Administrator, or provide the Administrator username and password upon opening the awarding. The Administrator account should already be added to the domain.

If errors occurred during installation process:

• The error bulletin should already include the failure reason, and the appropriate actions to have if possible.
• If errors exercise not suggest actions to resolve, the trouble could exist caused past 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 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 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 then retry installation.

Agent disconnected

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

Diagnosis / Investigation

• Check the network wellness on the estimator on which the agent is installed.
• If the password of the logged-in Tenant Administrator business relationship has changed, or whatsoever other similar, disquisitional 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 amanuensis failed to auto-upgrade, the version is likely besides onetime. Reinstall the agent.
• Token expiration can likewise cause the agent to disconnect.

Mitigation

• If there'southward a network upshot, fix that. The agent should reconnect soon after.
• If there are critical changes to the Tenant Admin account that require y'all to re-sign in: Reinstall the agent on all the computers.
• If neither of these condition applies, start past reinstalling the agent commencement.

Chore stuck in "Queued" condition

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

Diagnosis / Investigation

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

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 aforementioned. Sometimes it will set the trouble.

Task Report cannot be downloaded

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

• The Download task study link is disabled.
• The Download task report link displays active, but nix happens later clicking on it

Diagnosis / Investigation

• The link, "Download task report", is disabled until the task is finished. Reports are only available after the status of the job has become "Complete" or "Failed". Tasks that failed due to fourth dimension-out volition besides have a disabled task written report link.
• If no reports can be downloaded for finished, non-timed-out tasks, well-nigh likely there are errors that have occurred during the migration process which interrupted the uploading of the reports to SharePoint. Yet, they tin exist establish locally as long as they be.

Mitigation

On the figurer that completed the chore, effort 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. Discover the subfolder whose modified time is the closest to the task's start time. If the job reports exist, they will exist in the "Written report" folder within this subfolder.

Or

• If the chore 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'due south first time. The error written report will be in this subfolder.

Migration errors in task reports

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

Diagnosis / Investigation

• The failure reasons should already be 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 Observe the specific error here for more data: Fault codes.

If you lot receive an error like 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 two migration applications as exceptions so that the migration traffic won't be interrupted:

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

Google fault written report shows HTML lawmaking in report

Issue Fault reports generated for a Google migration will sometimes have HTML lawmaking 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 fault.

Mitigation Run less concurrent transations.

Status This is a known outcome. ETA not fix.

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 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, 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, nether Roles, select Manage roles.
3. Select the admin part that you want to assign to the user. If you don't see the role you're looking for, select Show all at the bottom of the listing.

SharePoint admin roles that were created as a upshot of joining an Azure group are non fully supported past Migration 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 role.

1. In the admin center, go to the Users > Agile users page.
2. On the Active users page, select the user whose admin function you desire 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 yous don't see the role you're looking for, select Bear witness all at the bottom of the list.

Error codes

Fault Code	Recommended action
0x00000000	Unexpected error.
0x01110001	Unknown reason.
0x0111000B	Path is too long.
0x0111000F	The parent folder was non migrated. Check the failure report to determine the file and then try again.
0x01110003	Cannot access source binder.
0x01110009	Cound non recollect the file metadata.
0x01110010	Invalid characters in the file proper noun. Check report for files names with <>:"?*/,
0x01110011	The item "created time" or "modified fourth dimension" is not supported.
0x0201000D	Cheque if the listing exists or if you 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 then reenter your username and password.
0x02010017	You lot must be a site collection admin.
0x02060009	1 - The site drove cannot be created because 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 be created or updated.
0x02060007	i - 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.
0x02010018	1 - Check your credentials and and so try once again.
	ii - A problem occurred accessing SharePoint.  Cheque your credentials and endeavour again.
	3 - A trouble occurred accessing SharePoint.  Check your credentials and your network connection and try once more.
	4 - A problem occurred accessing SharePoint.  Bank check your credentials and your site URL for accuracy and try once again.
	five - A problem occurred accessing SharePoint.  Check your credentials and the format of your URL. Retry.
	6 - A trouble occurred accessing SharePoint.  Bank check your credentials and try once again.  If the trouble continues, please create a support example.
	seven - A problem occurred accessing SharePoint.  Check your credentials and try opening your site in a browser.
0x0204000A	Cannot create packet file. All files and folders in the Migration Managing director working binder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02030001	i - Check your credentials. Restart your migration.
	2 - Check your credentials. Restart your migration.
	three - Check your credentials and your network connection. Restart your migration.
	four - Cheque your credentials and your site URL. Restart your migration.
	5 - Check your credentials and the format of your URL. Restart your migration.
	6 - Bank check your credentials and restart your migration. If this continues, please a support example.
	vii - 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 access it.
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 can access the source sites from a browser, and so create a support case.
0x02010010	Brand sure the source list and target listing accept 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 figurer is besides low. Migration Manager caches the parcel on the working folder. Expand your temporary storage and retry.
0x02030003	In that location are besides 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 parcel 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 airtight. Restart your migration.
0x02040009	The packet can't be created because the directory cannot be found. All files and folders in the Migration Manager working binder, %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 admission the URL via a browser. If this is a OneDrive business relationship, brand sure it has been pre-provisioned before you migrate.
0x0207001	You lot practise not take access to the task folder. Check if y'all 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 take been included in your migration telescopic.
0x01510001	Packages failed to upload. If you have customized Azure storage, bank check if yous can admission the Azure storage and check if you tin can access the target site. Endeavor migrating once more.
0x01510001	Failed to Upload the Job to Server: Upload file failed during migration.
0x02070009	Several packages failed to upload. Interruption the task and check your network connexion.
0x01710009	A failure occurred due to chore 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 parcel 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 folder proper name. The item may be 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.

Feedback

Submit and view feedback for

dullwored1953.blogspot.com

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

Share this post