Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - 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 Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Showing and Hiding Connection Adapter Buttons in the Ribbon Menu

Question

I am trying to make a connection to my source Blog/Wiki but I don't see the correct Connection type I need in the Metalogix Content Matrix Ribbon menu. Can I still make a connection?

I had previously made a connection to my source environment, and I need/want to make another connection to it, but I don't see the connection adapter I previously used in the Ribbon. Can I still make another connection to my source?

In the Metalogix Content Matrix Console - Blogs and Wikis Edition's Connection tab in the Ribbon menu I only see options for Confluence, RSS Feeds, MediaWiki, and MetaWeblog. Can Blogs and Wikis Edition make any other connection types?

Answer

The answer to all three of the above questions is: Yes, you can still make a connection to a supported source environment, even if you no longer see the correct connection adapter in the Ribbon menu by default. In Metalogix Content Matrix Console - Blogs and Wikis Edition version 7.2.1 and later a change has been made to only display the most popular Blog/Wiki connection types by default. The other connection types are still possible but the connection button for them is now hidden by default, however, it is possible to make the button visible again and use it to create a connection of that type. Below is a list of the connection types that are displayed by default, and a list of the connection types that are hidden by default. This page will also review how to enable the connection so it can be seen and used in the Ribbon menu.

Connections Displayed by Default

·Confluence

·RSS Feeds

·MediaWiki

·MetaWeblog

Note: A connection to a Intelligent source environment is made using the MetaWeblog connection adapter.

Connections Hidden by Default

·Atom Feed

·Blogger

·WordPress

Showing/Hiding Connection Buttons in the Ribbon Menu

The above listed hidden connection types can be configured to have their connection button displayed in the Ribbon menu. This can be done by making a change in one of the ApplicationSettings.xml Environmental Settings XML file for Metalogix Content Matrix, then restarting the client application. This section will review how to make this change. This change will ONLY apply to the connection types that are hidden by default.

1.First, close Metalogix Content Matrix if it is currently open.

2.Next, open a browser window for the file system that Metalogix Content Matrix is installed on and navigate to the following folder location:

§Microsoft Vista/Windows 7/Windows 8/Windows
<Drive>>\Users\<USER>\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - Blogs and Wikis Edition

§Microsoft Windows XP based systems (Windows 98, Windows Me, Windows 2000, Windows 2003, and Windows XP):
<Drive>>\Documents and Settings\<USER>\Application Data\Metalogix\Metalogix Content Matrix Console - Blogs and Wikis Edition

3.Open the ApplicationSettings.xml file in an editor program, such as NotePad, etc.

4.In this file, near the bottom, you should notice entries for ShowBloggerConnection, ShowAtomFeedConnection, and ShowWordPressConnection. These are entries to show or hide the Blogger connection, the Atom Feed connection, and the WordPress connection respectively. The values for these entries will be set to False by default.

5.If the value is currently set as False, then changing it to True will make the connection button visible in the Ribbon menu.

6.If the value is currently set as True, then users can change it to False if they want to hide the button from the Ribbon menu again.

NOTE:  If a connection to one of the default hidden connection types already exists, and users upgrade to Metalogix Content Matrix version 7.2 and later, that connection will still be visible and working in the Explorer View tab. However, if users want to add a New connection, the button will need to be made visible (i.e. the value set to "True") before it can be made by using the button in the Ribbon menu.

7.After the change has been made to show or hide the desired connection button in the Ribbon, save and close the ApplicationSettings.xml file.

8.Restart the Metalogix Content Matrix Console - Blogs and Wikis Edition client application. You should now see the change in the Ribbon menu (either the desired connection button is now visible, or the desired connection button is now hidden again).

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

Question

While trying to make a connection to an O365 modern team site 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

Answer

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

OR

·use Office 365 ADFS authentication to connect.

See also Connecting to an SPO Modern Team Site.

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

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.

Related Documents