Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - Blogs and Wikis Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Source Blog and Wiki Structure Connecting to a Source Blog or Wiki Connecting to SharePoint Preparing for Your Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Running Link Correction as a Post-Migration Task 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.Blog.Commands
Modifying Content Matrix Configuration and Settings Frequently Asked Questions About Us

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.

About Us

We are more than just a name

We are on a quest to make your information technology work harder for you. That is why we build community-driven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation™.

Our brand, our vision. Together.

Our  logo reflects  our story: innovation,  community and support. An important part of this story begins with the letter Q.  It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.

Contacting Quest

For sales or other inquiries, visit

Technical Support Resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

·Submit and manage a Service Request

·View Knowledge Base articles

·Sign up for product notifications

·Download software and technical documentation

·View how-to-videos

·Engage in community discussions

·Chat with support engineers online

·View services to assist you with your product


Related Documents