Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Copying SharePoint Objects as a Separate Action Self-Service Migration Incremental Migration Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed and Self-Service Migration Frequently Asked Questions
DB_Owner Permission Migrating with the Fabulous 40 Templates Item Count Discrepancies Keyboard Shortcuts License Key Troubleshooting Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Using Proxies, Load Balancing or Alternate Access Mappings Troubleshooting the Extensions Web Service Installing the Extensions Web Service on Specific Systems Extensions Web Service Installation Files Using Older Versions of the Extensions Web Service Preserving IDs when Migrating a Custom List as a Folder Migrating JavaScript Migrating Site Variations Migrating with SharePoint 2010/2013/2016 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and 2016 Site Collection Creation Issue Job List Database fails to Load After Upgrade Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs with a CSOM Connection Type Retrying Failed Document Copies to O365 CSOM Connections Migrating Content When the Source Custom List Template is Missing Are SharePoint Online Migrations Throttled? What to Expect when Migrating with StoragePoint on the Target Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)' How do I Remove Items from My Azure Blob Storage Account? Azure Batches Getting Stuck Supported Nintex Actions for SPO Migration "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication Error Making a Browser-Based Connection with PowerShell Console Open
About Us

What to Expect when Migrating with StoragePoint on the Target

Question

I am migrating content to my target SharePoint environment and I have Metalogix StoragePoint installed. What kind of results should I expect after migration?

Answer

There are a number of different behaviors to expect when migrating to a target SharePoint environment that has Metalogix StoragePoint installed. The different results you will see depend on which option is selected in the StoragePoint Options tab. For more information about these options, please see Copy Options Dialog.

NOTE:  For the StoragePoint options to be available, all of the following must be true:
 •  StoragePoint 5.1 must be installed on the target environment.
 •  The target environment does not have a CSOM connection type.

The following is a breakdown of expected results:

StoragePoint Options - Successful Outcome

·Add documents to StoragePoint if an endpoint is configured - This option is for when content from a non-externalized environment (a source environment that does not have StoragePoint installed) is being migrated into an externalized SharePoint target. In this case, any of the files or documents that are included in the migration will be externalized, meaning that those files and documents will call StoragePoint as they are being migrated, and will be externalized directly with the reference link left behind in the file or document's place (in the target SharePoint environment). Once the migration is complete, users can navigate to one of the migrated documents in Metalogix Content Matrix, switch to the Items View, right-click the document, and then select StoragePoint Details. Here, users should be able to see the StoragePoint endpoint folder location for the externalized content, as well as the externalized file name. If the document is opened through SharePoint directly, it will open as expected.

·Shallow Copy of Externalized Data - Shallow copying is no longer supported in Metalogix Content Matrix. For more information, please see Shallow Copying Externalized Content.

·None - This option is for cases where Metalogix StoragePoint is not installed on the target SharePoint environment, or for cases where StoragePoint is installed but users do not want to use it as part of the migration process. When this option is selected, content will be migrated directly into SharePoint with all StoragePoint-related features ignored. However, if the target environment is configured to be externalized with StoragePoint, it is possible that the content will be migrated into the SharePoint target as if the StoragePoint options are ignored, but the target SharePoint environment would then externalize the content separately after the migration completes. While the end result would be the externalization of the data, the migration process itself is only migrating content directly into the SharePoint target.

StoragePoint Options - Unsuccessful Outcome

·Add documents to StoragePoint if an endpoint is configured - If this option failed to migrate the documents/files into StoragePoint, then when users go to the StoragePoint Details, there will be nothing set. This indicates that the files were not placed into the StoragePoint EndPoint and were not externalized.

·Shallow Copy of Externalized Data - Shallow copying is no longer supported in Metalogix Content Matrix. For more information, please see Shallow Copying Externalized Content.

·None - If this option is selected but fails, then the content migration to the target will have failed. This means that the documents/files that are included in the migration action will not exist on the target (externalized or not).

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

Question

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).

CONTEN~1_img247

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

Answer

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.

How do I Remove Items from My Azure Blob Storage Account?

Question

I am running out of storage space in my Azure blob storage account. How do I remove Azure blob storage containers or queue containers from my blob storage account to free up space for more migration actions?

Answer

A prerequisite to removing items is that Azure PowerShell must be installed and configured. For instructions on how to do this, please see the following link: https://azure.microsoft.com/en-us/documentation/articles/powershell-install-configure/.

To remove blob storage containers or queue containers from your Azure blob storage account, do the following:

1.Ensure there are no active migration actions running that use the Azure storage where the items are stored.

2.Open Azure PowerShell.

3.Connect to Azure using the New-AzureStorageContext Cmdlet. Your account name and account key are required parameters. Note that these are different from your Client ID and Application Secret.        $context = New-AzureStorageContext -StorageAccountName $accountName -StorageAccountKey $accountKey

4.Get the items using either the Get-AzureStorageContainer or the Get-AzureStorageQueue Cmdlet. A sample call is shown below:

$containers = Get-AzureStorageContainer -Context $context

5.Remove the items using either the Remove-AzureStorageContainer or the Remove-AzureStorageQueue Cmdlet, depending on the item type retrieved in the previous step. A sample call is shown below:

$containers | %{Remove-AzureStorageContainer -Name $_.Name -Context $context -Force}

6.All items of the specified type are now removed from your Azure blob storage account.

NOTE: In the majority of cases, these items are automatically removed after successful or canceled migrations. Typically, items will only accumulate when the import logs associated with the successful migration of a batch fail to download.

Azure Batches Getting Stuck

Question

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?

Answer

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).

Related Documents