Retrying Failed Document Copies to O365 CSOM Connections
Question
When I try to migrate some of my content into O365 using a SharePoint CSOM 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 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 O365 specific methods.
1.Make sure that the Metalogix Content Matrix client application is closed.
2.In the file system that the Metalogix 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 Metalogix 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 Metalogix 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 Metalogix Content Matrix client application. The changes should now be in Metalogix 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.
Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment
Question
Why am I getting an error when I try to connect to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-enabled environment?
Answer
Content Matrix uses some assemblies for FIPS compliance that are not supported for certain SharePoint 2019 and SharePoint Server Subscription Edition connections.
For a remote object model (MEWS) connection (displays for the top node) for SharePoint 2019:
Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: -- <!DOCTYPE html> <html>
For a local object model (OM) connection (displays at the item level for SharePoint 2019 and SharePoint Server Subscription Edition):
The type initializer for 'Microsoft.SharePoint.ApplicationRuntime.SPRequestModule' threw an exception
In addition, errors will display in Browser View and Items View.
For SharePoint Server Subscription Edition, you can connect using a remote object model (MEWS) connection.
Error Making a Browser-Based Connection with PowerShell Console Open
Question
Why do I get a "Manual Reconnection Required" error when I try to run a Metalogix Content Matrix job using PowerShell?
Answer
This error would occur if you used the Metalogix Content Matrix Console to connect to a SharePoint target with Web Browser Authentication while the PowerShell console is open. To avoid this issue, take the following steps:
1.Make sure that the PowerShell console is closed at the time you make a target connection via the Metalogix Content Matrix Console when Web Browser Authentication is used.
NOTE: After entering your credentials, be sure to check the Remember my Password box, as credentials must be stored in the Credential Manager vault before the connection is made.
2.After you have created your PowerShell job, close the Metalogix Content Matrix Console.
NOTE: At this point, it is recommended that you remove your Web Browser Authentication credentials from Windows Credential Manager. You will be prompted to re-enter them when the PowerShell job is run.
3.Launch the PowerShell console and run the job.
4.When prompted, re-enter the credentials you used to connect via the Metalogix Content Matrix Console. (Again, remember to check the Remember my password box.)
Support for GCC High Tenants
Question
Does Content Matrix support SharePoint Online GCC High connections?
Answer
Refer to the following table for specific target connections that Content Matrix supports for GCC High tenants.
IMPORTANT: In order to use ADFS authentication with a GCC High tenant you must first run a utility provided by Quest Support and enable the setting EnableUserProvidedAuthentication. Refer to the Quest Support Knowledge Base article Enabling User Provided Authentication in Content Matrix for details.
|
OAuth |
OAuth with MFA |
ADFS |
ADFS |
Web Browser Authentication |
Office 365 Web Browser Authentication |
|---|---|---|---|---|---|
|
-- |
|
-- |
-- |
|
|
|
-- |
|
-- |
|
|
|
