Retrying Failed Document Copies to O365 CSOM Connections
Question
When I try to migrate some of my content into Microsoft 365 using a SharePoint CSOM or Microsoft 365 Tenant connection type, and this content contains a large Document Library, I see that some of my documents fail to migrate. The logs for the failure indicate that a "HTTP 500 - Internal Server Error" was thrown. What is the cause of this? And how can I fix it?
Answer
There is a potential issue when migrating specifically to SharePoint Online where users can encounter an "HTTP 500" error. This is caused by a combination of the CSOM/Tenant connection adapter and SharePoint's document upload methods. To help resolve this issue there is a document retry feature that can be configured. This retry feature will attempt to upload the document(s) into the SharePoint Online target, and depending on the configured setting, will attempt to retry the upload process if it fails or times-out on the initial try.
The below steps will explain how to enable and configure this retry setting.
NOTE: This retry method is only meant for migrating to SharePoint Online targets. If you are migrating to an on premises target, then this retry feature will not benefit you since it makes use of Microsoft 365 specific methods.
1.Make sure that the Content Matrix client application is closed.
2.In the file system that the Content Matrix Console client application is installed on, navigate to the the appropriate file location:
·If you are required to be a local administrator on the machine where Content Matrix is installed: C:\ProgramData\Metalogix
OR
·If you are not required to be a local administrator on the machine where Content Matrix is installed: C:\Users\<username>\AppData\Roaming\Metalogix\Common
3.In this location there should be an EnvironmentSettings.xml file. Open this file in an editor program. For example, Notepad, etc.
4.There are two variables that will need to be modified in order for the retry method to work. They are:
·CSOMDocumentRetriesNumber - This value determines the number of times that Content Matrix will make another attempt to upload/migrate any document(s) that has failed the initial document upload try, when migrating to a SharePoint Online CSOM target.
·CSOMDocumentRetriesDelay - This value determines the amount of time, in seconds (s), that Content Matrix will wait before starting a document upload retry, and is based on the above ("CSOMDocumentRetriesNumber") variable.
NOTE: The default values for these two variables will be set as "0". Users can set these values as desired, based on what works best for their environment.
5.After the desired values have been entered in the two variables, save and close the file.
6.Restart the Content Matrix client application. The changes should now be in Content Matrix Console, and used when running any migration to a SharePoint Online target environment.
After these values have been set and the client application has been restarted, any documents that fail on the initial migration attempt we be retried.
IMPORTANT: If these steps do not resolve the issue and you are using the Import Pipeline for the migration, the error may be pipeline-related. See "Error, the batch will be resubmitted" Message Displays When Using the Import Pipeline for details.
Import Pipeline Batches Getting Stuck
Question
I am migrating some content using the Import Pipeline. After some time the batches seem to simply stop. Why am I facing this issue?
Answer
Migration duration and overall performance using the the Import Pipeline may vary due to factors outside the control of Content Matrix. Migration processing resides within Microsoft's domain and is subject to Microsoft's internal processes, such as maintenance and upgrades.
You may experience a delay of several hours before batch completion if the machines that Microsoft uses undergo maintenance/upgrades or if there are Microsoft 365 service issues/outages (as can be seen in the Microsoft 365 Admin Center under Service Health).
Error: 'The object is associated with property AssociatedMemberGroup.'
Question
When attempting to copy an object to a SharePoint Online site or OneDrive, why do I receive the following error?
Object reference not set to an instance of an object on server. The object is associated with property AssociatedMemberGroup.
Answer
This error may occur when one or more of the default SharePoint groups (Owners, Members, and/or Visitors) are not present on the target.
NOTE: For OneDrives, none of these groups are present by default.
Create the missing default group(s) on the target. Refer to the applicable Content Matrix Knowledge Base article for more information.
Migration Error: 'ERROR, the batch will be resubmitted to the import pipeline'
Question
What does it mean when the message ERROR, the batch will be resubmitted to the import pipeline displays in the Information section of the Log Item Details dialog when a migration is performed using the Import Pipeline?
Answer
You may see this message (which will begin with either ERROR or FATAL ERROR) during a migration when a batch fails to migrate in its entirety. To address this issue, increase the value of the environmentsettings.xml key MaxAzureBatchRetryCount. This key controls the maximum number of times Content Matrix will resubmit the batch until it is successfully migrated. (The default value is 5.)
The batch retry mechanism will also be triggered for the following errors:
·Please try again. CallStack -- at Microsoft.SharePoint messages
·Access denied
·Save Conflict The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
·Updates to system roles is not allowed.
·List does not exist
For any error not listed above (such as Item Does Not Exist, which is different than List does not Exist), a batch will be resubmitted only if the error message is added to the environmentalsettings.xml key ErrorMessagesForRetryAzureBatch.
IMPORTANT: If adjusting this setting does not resolve the issue, the error may be with the CSOM connection. See Retrying Failed Document Copies to SharePoint Online CSOM Connections for details.