Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - File Share Edition User Guide

Introduction Entering the License Key Overview of Content Migration Content Matrix Console End User Interface Enabling Advanced Mode Enabling and Disabling Optimistic Mode Connecting to a File System Connecting to SharePoint Migrating to O365 Using the Azure Pipeline Preparing for Your Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix Content Matrix PowerShell Commandlet List
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Azure Batches Getting Stuck


I am migrating some content through the Azure SPO Pipeline. After some time the Azure batches seem to simply stop. Why am I facing this issue?


Migration duration and overall performance using the Azure SPO Pipeline may vary due to factors outside the control of Metalogix Content Matrix. The pipeline that processes migration 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 for the pipeline undergo maintenance/upgrades or if there are O365 service issues/outages (as can be seen in the O365 Admin Center under Service Health).

"Error, the batch will be resubmitted" Message Displays When Using Azure


What does it mean when the message ERROR, the batch will be resubmitted to the migration pipeline displays in the Information section of the Log Item Details dialog when a migration is performed using the Azure Pipeline?

Azure Migration Error


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 O365 CSOM Connections for details.

Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)'


I am migrating some content and getting the following error: Exception: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).


What is this error? Why am I getting it? And how can I resolve it?


The error message is thrown due to a timeout on an internal call in Metalogix Content Matrix, and users can resolve the issue.

When a user tries to run an action within the Metalogix Content Matrix client application, there are some internal processes and calls that happen before Metalogix Content Matrix actually starts sending data over to the target environment. The "There was an error reading from the pipe..." message is caused when one of these internal calls/processes encounters a timeout issue as it is moving the content, and results in the item failing to copy (or the setting failing to be configured). This issue is mainly encountered when migrating to a target environment using a Client Side Object Model (CSOM) connection type.

To resolve the issue, there are a set of four configurable timeout variables, which will prevent the timeout issue from happening. These timeout variables are in the EnvironmentSettings.xml file. The below steps will review which variables will need to be changed, and how to change them.

1.First, make sure that the Metalogix Content Matrix client application is closed. If it is currently open, it will need to be closed before continuing.

2.Next, navigate to the EnvironmentSettings.xml file. Please see the Configuration Variables Files page for more details on accessing this file.

3.Open the EnvironmentSettings.xml file in an editor program (like NotePad, etc.). There are a set of four values that can be edited to help resolve the "There was an error reading from the pipe..." message, and all four of these variables should be changed. They are:

a.PipeCloseTimeout - The default Metalogix Content Matrix value for this setting is 15 minutes.

b.PipeOpenTimeout - The default Metalogix Content Matrix value for this setting is 15 minutes.

c.PipeReceiveTimeout - The default Metalogix Content Matrix value for this setting is 20 minutes.

d.PipeSendTimeout - The default Metalogix Content Matrix value for this setting is 15 minutes.

NOTE: All four of these variables are set in minutes.

While it is possible to set the Metalogix Content Matrix default values to be lower, it is not recommended, especially if the "There was an error reading from the pipe..." message is returned. However, in the case that users want to lower these values they can only be reduced as far down as the Microsoft default values. These are 1, 1, 10, and 1 respectively.

4.Set the values for the four fields to be higher than the Metalogix Content Matrix default values. Then save and close the EnvironmentSettings.xml file.

5.Restart the Metalogix Content Matrix client application and run the migration again. If the four variable settings have been set high enough, the error message "There was an error reading from the pipe: The pipe has been ended. (109, 0x6d)" should no longer be thrown.

"Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication


While trying to make a connection to an O365 modern team site using Web Browser authentication, or when trying to load it in the Console after successfully making a tenant-level connection using Web Browser authentication, a Login Browser popped up with the message You need permission to access this site.  Why?

Modern Team Site Perms Error


When using Web Browser Authentication, the login account must be a Site Collection Administrator (Site Owner).  You can either:

·make sure the account you are using to connect is a Site Collection Administrator


·use Office 365 ADFS authentication to connect.

See also Connecting to an SPO Modern Team Site.

Related Documents