Migrating Currently Please Try Again Later

Skip to main content

Troubleshoot Migration Manager issues and errors

• Commodity
• 05/09/2022
• thirteen minutes to read

Is this page helpful?

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

In this article

This article describes how to resolve issues and errors yous may experience when using Migration Manager.

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

Bank check 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 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 migrate. You tin do this using a script, every bit shown here: Pre-provision OneDrive for users in your organisation.

Agent error messages

Message	Action
Migration amanuensis could non be installed. Close setup and endeavor again.	You may exist using an out-of-engagement version of the amanuensis setup file to install the agent. See Amanuensis installation failure below for more information.
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 account associated with the agent has read permissions to the file share you lot 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 business relationship associated with the agent has read permissions to the file share you want to migrate.

Destination site URL issues

Message	Recommended action
Destination site or web does not exist	Ostend the destination site or subsite exists. If OneDrive account, brand certain that it has been pre-provisioned.
Failed to bank check site or web existence.	Ostend the destination site or subsite exists.

Frequently seen error messages

Message	Recommended activeness
Invalid source folder	Confirm the path you entered is correct and follows the proper format Confirm you accept read admission 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 still 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
Scan file failure: Target path is also 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 plenty deejay infinite to pack the file	The disk infinite available for the migration working folder is besides pocket-size for the size of your source file. Enlarge your size of your working binder try again.
Packaging failure: Cannot open up file	Packaging failed due to not-existing source. Check if you tin access the source root binder.
A indistinguishable task has already been created.	The CSV file used to practice bulk migration cannot have duplicate entries. Remove the duplicate line(s) and effort once more.
The parent folder was not migrated	The parent folder was not migrated, therefore all items under the binder will fail to migrate. Check your parent folder and retry your migration.

Agent installation failure

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

Diagnosis / Investigation

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

Mitigation

1. Become to the Migration centre in the SharePoint admin eye, and sign in with an account that has admin permissions for your organization.
2. Select Download agent setup file.
3. Run the clientsetup.exe file on the calculator or VM where you lot want to install the agent. Follow the instructions to complete the amanuensis installation.

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

Example:

Diagnosis / Investigation

If the clientsetup.exe cannot exist opened:

• Sign in to Windows as Administrator, or provide the Administrator username and password upon opening the application. 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 take if possible.
• If errors do not suggest actions to resolve, the problem could exist acquired by temporary network failure, or other unknown issues.

Mitigation

If the clientsetup.exe cannot be opened:

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

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 not-specific errors, make sure your Ambassador account has been added to the domain. Close the application window so retry installation.

Amanuensis disconnected

Issue: The "state" of the agent gets stuck as "Disconnected" and never comes dorsum.

Diagnosis / Investigation

• Check the network wellness on the computer on which the agent is installed.
• If the password of the logged-in Tenant Administrator account has changed, or whatever other similar, disquisitional changes practical to the Tenant Admin account that would crave re-sign in, all of the agents volition be disconnected and reinstallation is required on all of them.
• If the agent failed to car-upgrade, the version is likely too old. Reinstall the amanuensis.
• Token expiration tin also cause the amanuensis to disconnect.

Mitigation

• If there's a network effect, set that. The agent should reconnect presently after.
• If there are critical 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, kickoff by reinstalling the agent showtime.

Task stuck in "Queued" condition

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

Diagnosis / Investigation

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

Mitigation

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

Chore Written report cannot be downloaded

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

• The Download task report link is disabled.
• The Download task report link displays agile, but naught happens after clicking on information technology

Diagnosis / Investigation

• The link, "Download job study", is disabled until the task is finished. Reports are but available later the status of the task has get "Complete" or "Failed". Tasks that failed due to time-out will also have a disabled task report link.
• If no reports tin be downloaded for finished, non-timed-out tasks, nigh probable there are errors that take occurred during the migration procedure which interrupted the uploading of the reports to SharePoint. Nonetheless, they tin exist institute locally as long as they exist.

Mitigation

On the computer that completed the job, attempt to remember the reports.

• In binder %AppData%\Microsoft\SPMigration\Logs\Migration\MigrationTool[tenant_site], or < Your-Customized-Working-Folder >\Migration\MigrationTool[tenant_site], sort the subfolders past their modified time. Find the subfolder whose modified fourth dimension is the closest to the task's get-go time. If the job reports exist, they will be in the "Report" folder inside this subfolder.

Or

• If the task has failed, navigate to the binder %AppData%\Microsoft\SPMigration\Logs, then sort the subfolders by their modified fourth dimension. Find the subfolder whose modified time is the closest to the task's starting time time. The error report will be in this subfolder.

Migration errors in task reports

Effect Migration tasks neglect due to various reasons and are detailed in the task reports.

Diagnosis / Investigation

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

• If y'all tin't download the task reports, please refer to Task Written report Cannot Be Downloaded

Mitigation Find the specific error here for more information: Error codes.

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

Check the settings on any AntiVirus application installed on the agent auto. Add our two migration applications as exceptions and then that the migration traffic won't be interrupted:

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

Google error study shows HTML code in study

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

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.

Condition This is a known issue. ETA not set.

Geo admins not supported

Migration Manager currently doesn't support the Geo admin office for specific scenarios. For file share migrations, these users tin can't access the scans tab. For cloud 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 office.

1. In the admin center, go to the Users > Active users page.
2. On the Agile 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 y'all're looking for, select Evidence all at the bottom of the list.

SharePoint admin roles that were created as a outcome of joining an Azure grouping are not fully supported past Migration Director. 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. Until this is resolved, assigned the user either a SharePoint admin or Global admin part.

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

Error codes

Mistake Code	Recommended action
0x00000000	Unexpected mistake.
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 try again.
0x01110003	Cannot admission source folder.
0x01110009	Cound not recollect the file metadata.
0x01110010	Invalid characters in the file name. Bank 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 yous can admission information technology 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 then reenter your username and password.
0x02010017	Y'all must exist a site collection admin.
0x02060009	1 - The site drove cannot be created because the URL is already in utilise or an invalid URL.
	two - The site collection cannot be created considering the URL contains invalid grapheme.
	iii - The site collection cannot be created or updated.
0x02060007	one - The site collection cannot be created because the URL is already in use or an invalid URL.
	two - The site drove cannot exist created because the URL contains invalid graphic symbol.
0x02010018	1 - Check your credentials and and so effort again.
	ii - A problem occurred accessing SharePoint.  Cheque your credentials and effort again.
	iii - A trouble occurred accessing SharePoint.  Check your credentials and your network connectedness and try again.
	4 - A problem occurred accessing SharePoint.  Cheque 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.  Bank check your credentials and endeavour once again.  If the trouble continues, please create a support case.
	vii - 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 exist closed. Restart your migration.
0x02030001	one - Check your credentials. Restart your migration.
	two - Check your credentials. Restart your migration.
	3 - Cheque your credentials and your network connexion. Restart your migration.
	4 - Cheque your credentials and your site URL. Restart your migration.
	5 - Check your credentials and the format of your URL. Restart your migration.
	half dozen - Bank 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	Ostend the path and format of the user-mapping file and that you lot accept permission to admission information technology.
0x02050001	All files and folders in the Migration Manager working binder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist closed. Restart your migration.
0x02010002	Check your network status. If yous can access the source sites from a browser, then create a back up case.
0x02010010	Brand sure the source list and target list have the same template.
0x0204000D	All files and folders in the Migration Managing director working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist airtight during migration. Restart your migration.
0x02040012	The temporary storage on your local calculator is too low. Migration Managing director caches the packet on the working binder. Expand your temporary storage and retry.
0x02030003	At that place 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 Director working folder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must be closed. Restart your migration.
0x02040009	The packet can't exist created because the directory cannot be institute. All files and folders in the Migration Manager working binder, %appdata%\Microsoft\SPMigration\Logs\Migration\MigrationToolStorage, must exist closed. Restart your migration.
0x02010020	Disable migrating version history in Migration Manager settings or enable versioning in SPO.
0x0201000E	Bank 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 certain it has been pre-provisioned before y'all migrate.
0x0207001	You do not have access to the task folder. Check if you 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 you have customized Azure storage, check if you lot can access the Azure storage and check if y'all tin can access the target site. Try migrating again.
0x01510001	Failed to Upload the Chore to Server: Upload file failed during migration.
0x02070009	Several packages failed to upload. Pause the chore and check your network connection.
0x01710009	A failure occurred due to task end failures; some items failed in the package. 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 Error.
0x01710004	Errors or timeout for server processing the file. Fail to expect upwardly folder name. The item may be in other list or site in the same site collection. Or the particular is in the recycle bin.
0x0131000F	Failed to Read the file. File is checked out.

Feedback

Submit and view feedback for

eatonshood1967.blogspot.com

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