Migration Remediation Best Practices

Learn DryvIQ's recommendations for remediating items.

Updated at May 16th, 2025

+ More

Table of Contents

Overview Flagged Item Messages A connection was successfully established with the server, but an error occurred during the pre-login handshake. Azure did not respond with status of the current batch operation. Please retry the operation. Bad Request [code=bad_request] Cannot access a disposed object Connection Timeout Expired Disconnected from the root Error=Value=CobaltAllZerosDetected, Tag=0x0121d3da CallStack -- at Cobalt.RequestBatch.ThrowIfAnyError() Execution Timeout Expired Incomplete chunked upload. CallStack -- at Microsoft. SharePoint.Deployment. FileSerializer.UploadFileInChunksV2 Invalid path '/PATH/FILENAME' {ERROR} Invalid path '/PATH/FILENAME' exceeds maximum total length of 400 Invalid path 'FILENAME': Unable to build duplicate file name Method Not Allowed [code=method_not_allowed] Object reference not set to an instance of an object. Please contact support to help with this error. One or more errors occurred... Response status code does not indicate success Source path not found: /. Please restore the original folder or provide a new folder. The file or folder name "{FILENAME}" contains invalid characters. Please use a different name. Common invalid characters include the following: # % * : < > ? / The item could not be located within the storage platform: /PATH/FILENAME The item or associated version could not be located within the storage platform: /PATH/FILENAME (Operation 'PortalArchitects.Connectors.Transfers.GetVersionsOperation') The name from body should match the name specified in the url [code=invalidRequest] The path exceeds the maximum number of 10,000 children: /PATH The request failed to run because the batch is aborted The SSL connection could not be established, see inner exception. The tracking information for item XXXXXXX is disconnected from the root. The URL 'PATH/FILENAME' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web. This file has been identified as malware or spam and cannot be downloaded. [code=cannotDownloadAbusiveFile] This SqlTransaction has completed; it is no longer usable. Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. Valid SharePoint server, but unable to determine a valid site URL from the one entered Value cannot be null. A rate limit exception occurred. Account deactivated An impersonated connection could not be made using the Account The connection is not active ('xxxxxxxxxxxxxxxxxxxxxx'). Please edit the authentication information in order to repair the connection. This site has exceeded its maximum file storage limit

Overview

Items are flagged for various reasons during a migration, and steps can be taken to ensure minimal flagged items throughout the various migration stages. This page provides DryvIQ’s best practices for remediating flagged items throughout the simulation and migration stages. Following these best practices is key to a successful migration.

Below is a list of the common messages that accompany flagged items. For each message, DryvIQ provides actions you can take during each migration stage when you experience this error. The suggestions are divided into four categories:

Proactive Solution: These are steps you should take before running a simulation job to reduce flagged items due to the corresponding message.
Post Simulation Action: These are steps you can take after running a simulation job to fix flagged items before converting the job to a transfer job.
Post Migration Action: These are steps you need to take to transfer the flagged items to the destination.
Job Failure Action: If the flagged item message causes job failure (the job fails to run), these are the steps you need to take to correct the issue so the job can run.

Flagged Item Messages

Expand the error message below to review DryvIQ’s remediation best practices.

Report: Flagged/Retry Items

Proactive
Solution

On
Simulation
Report

Post-Simulation
Action

On
Migration
Report

Post-Migration
Action

Causes
Job
Failure

Job
Failure
Action

Not

applicable

Yes

Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.

Yes

The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.

Not

applicable

Azure did not respond with status of the current batch operation. Please retry the operation.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Bad Request [code=bad_request]

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Cannot access a disposed object

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Connection Timeout Expired

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	Yes	Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Disconnected from the root

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	Yes	Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.

Error=Value=CobaltAllZerosDetected, Tag=0x0121d3da CallStack -- at Cobalt.RequestBatch.ThrowIfAnyError()

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Execution Timeout Expired

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	Yes	Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Incomplete chunked upload. CallStack -- at Microsoft. SharePoint.Deployment. FileSerializer.UploadFileInChunksV2

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Invalid path '/PATH/FILENAME' {ERROR}

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	Yes	Depending on the error, you may be able to rename the file/folder to correct this issue.	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Invalid path '/PATH/FILENAME' exceeds maximum total length of 400

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
This error will be shown in the simulations; however, you can scan the source using an alternative method (such as a custom PowerShell script) if you want to identify these issues before simulations.	Yes	Reduce the path to less than 400 characters. You will need to rearrange content so it is under 400 characters	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Invalid path 'FILENAME': Unable to build duplicate file name

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Method Not Allowed [code=method_not_allowed]

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Object reference not set to an instance of an object. Please contact support to help with this error.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

One or more errors occurred...

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Response status code does not indicate success

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	Yes	Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Source path not found: /. Please restore the original folder or provide a new folder.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Check that the paths you are using are available and that the appropriate permissions have been assigned before submitting them for a migration. You can scan the source using an alternative method (such as a custom PowerShell script).	Yes	The drive does not exist, or the Service Account does not have access to the drive.	Yes	The drive does not exist, or the Service Account does not have access to the drive.	No	Not applicable

The file or folder name "{FILENAME}" contains invalid characters. Please use a different name. Common invalid characters include the following: # % * : < > ? /

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	Yes	Depending on the error, you may be able to rename the file/folder to correct this issue.	Yes	Depending on the error, you may be able to rename the file/folder to correct this issue.	No	Not applicable

The item could not be located within the storage platform: /PATH/FILENAME

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

The item or associated version could not be located within the storage platform: /PATH/FILENAME (Operation 'PortalArchitects.Connectors.Transfers.GetVersionsOperation')

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

The name from body should match the name specified in the url [code=invalidRequest]

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

The path exceeds the maximum number of 10,000 children: /PATH

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
This error will be shown in the simulations; however, you can scan the source using an alternative method (such as a custom PowerShell script) if you want to identify these issues before simulations.	Yes	Fix the folder so it does not have more than 10,000 items (files or folders). Then, rerun the job. The error should clear up once the job runs again.	Yes	Fix the folder so it does not have more than 10,000 items (files or folders). Then, rerun the job. The error should clear up once the job runs again.	No	Not applicable

The request failed to run because the batch is aborted

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

The SSL connection could not be established, see inner exception.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Check that the site you are using is available and that the appropriate permissions have been assigned before submitting URLs for a migration. You can scan the source using an alternative method (such as a custom PowerShell script).	Yes	Check that the site you are using is available and that the appropriate permissions have been assigned before submitting URLs for a migration.	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

The tracking information for item XXXXXXX is disconnected from the root.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

The URL 'PATH/FILENAME' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

This file has been identified as malware or spam and cannot be downloaded. [code=cannotDownloadAbusiveFile]

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	Yes	Check for false positives.	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

This SqlTransaction has completed; it is no longer usable.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Valid SharePoint server, but unable to determine a valid site URL from the one entered

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Check that the site you are using is available and that the appropriate permissions have been assigned before submitting URLs for a migration. You can scan the source using an alternative method (such as a custom PowerShell script).	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

Value cannot be null.

Report: Flagged/Retry Items

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	No	Not applicable	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	No	Not applicable

A rate limit exception occurred.

Report: Job Failure Report

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	Yes	Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.	Yes	Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.	Yes	Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.

Account deactivated

Report: Job Failure Report

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Check the account(s) you are using before submitting them for a migration. Verify that the user is activated and the that appropriate permissions have been assigned. You can use a custom PowerShell script for this.	Yes	Check the account(s) you are using. Verify that the user is activated and that the appropriate permissions have been assigned. Fix account issues and rerun the job.	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	Yes	Check the account(s) you are using. Verify that the user is activated and that the appropriate permissions have been assigned. Fix account issues and rerun the job.

An impersonated connection could not be made using the Account

Report: Job Failure Report

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Check the account(s) you are using before submitting them for a migration. Verify that the user is activated and the that appropriate permissions have been assigned. You can use a custom PowerShell script for this.	Yes	Check the account(s) you are using. Verify that the user is activated and that the appropriate permissions have been assigned. Fix account issues and rerun the job.	Yes	The item(s) could not be migrated; the item(s) need to be manually copied from the source to the destination.	Yes	Check the account(s) you are using. Verify that the user is activated and that the appropriate permissions have been assigned. Fix account issues and rerun the job.

The connection is not active ('xxxxxxxxxxxxxxxxxxxxxx'). Please edit the authentication information in order to repair the connection.

Report: Job Failure Report

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Not applicable	Yes	Verify that the credentials used to create the connection have not expired/changed. If the credentials have changed, update the connection with the new credentials. If the credentials have not changed, contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.	Yes	Verify that the credentials used to create the connection have not expired/changed. If the credentials have changed, update the connection with the new credentials. If the credentials have not changed, contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.	Yes	Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.

Proactive
Solution

On
Simulation
Report

Post-Simulation
Action

On
Migration
Report

Post-Migration
Action

Causes
Job
Failure

Job
Failure
Action

Not
applicable

Yes

Verify that the credentials used to create the connection have not expired/changed.

If the credentials have changed, update the connection with the new credentials.

If the credentials have not changed, contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.

Yes

Verify that the credentials used to create the connection have not expired/changed.

If the credentials have changed, update the connection with the new credentials.

If the credentials have not changed, contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.

Yes

Contact your DryvIQ Consultative Services project representative or DryvIQ Customer Support.

This site has exceeded its maximum file storage limit

Report: Job Failure Report

Proactive Solution	On Simulation Report	Post-Simulation Action	On Migration Report	Post-Migration Action	Causes Job Failure	Job Failure Action
Check the total size of the source in the simulation reports (preferred) or use another method (such as a custom PowerShell script) to ensure the destination has adequate storage sizing based on the size of the source.	No	Not applicable	Yes	Increase the user/site storage and rerun the job.	Yes	Increase the user/site storage and rerun the job.

migration solutions relocation solutions

Migration Remediation Best Practices

Contact Us

Overview

Flagged Item Messages

A connection was successfully established with the server, but an error occurred during the pre-login handshake.

Azure did not respond with status of the current batch operation. Please retry the operation.

Bad Request [code=bad_request]

Cannot access a disposed object

Connection Timeout Expired

Disconnected from the root

Error=Value=CobaltAllZerosDetected, Tag=0x0121d3da CallStack -- at Cobalt.RequestBatch.ThrowIfAnyError()

Execution Timeout Expired

Incomplete chunked upload. CallStack -- at Microsoft. SharePoint.Deployment. FileSerializer.UploadFileInChunksV2

Invalid path '/PATH/FILENAME' {ERROR}

Invalid path '/PATH/FILENAME' exceeds maximum total length of 400

Invalid path 'FILENAME': Unable to build duplicate file name

Method Not Allowed [code=method_not_allowed]

Object reference not set to an instance of an object. Please contact support to help with this error.

One or more errors occurred...

Response status code does not indicate success

Source path not found: /. Please restore the original folder or provide a new folder.

The file or folder name "{FILENAME}" contains invalid characters. Please use a different name. Common invalid characters include the following: # % * : < > ? /

The item could not be located within the storage platform: /PATH/FILENAME

The item or associated version could not be located within the storage platform: /PATH/FILENAME (Operation 'PortalArchitects.Connectors.Transfers.GetVersionsOperation')

The name from body should match the name specified in the url [code=invalidRequest]

The path exceeds the maximum number of 10,000 children: /PATH

The request failed to run because the batch is aborted

The SSL connection could not be established, see inner exception.

The tracking information for item XXXXXXX is disconnected from the root.

The URL 'PATH/FILENAME' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.

This file has been identified as malware or spam and cannot be downloaded. [code=cannotDownloadAbusiveFile]

This SqlTransaction has completed; it is no longer usable.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Valid SharePoint server, but unable to determine a valid site URL from the one entered

Value cannot be null.

A rate limit exception occurred.

Account deactivated

An impersonated connection could not be made using the Account

The connection is not active ('xxxxxxxxxxxxxxxxxxxxxx'). Please edit the authentication information in order to repair the connection.

This site has exceeded its maximum file storage limit

Related Articles