Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to O365 Using the Azure Pipeline/SPO Containers 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 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and Later 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 "Error, the batch will be resubmitted" Message Displays When Using Azure Item Count at Target is Increased When Migrating Using the Azure Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Azure Pipeline 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

Extensions Web Service Installation Files


Before I can install the Metalogix SharePoint Extensions Web Service I need to know specifically what files are installed, and where. Can this information be provided?


Yes, we can provide some information on what files are installed.

The Metalogix Extensions Web Service installs as a SharePoint solution (.WSP file) that is automatically deployed by the Web Service installer, and pushed out to all Web Front Ends (WFE's) in the farm. Inside the solution file are the necessary files for the Web Service. These files are:

·An ASMX file and two ASPX files, which are put in the SharePoint 14 hive (or the SharePoint 12 Hive, if migrating to SharePoint 2007). These three files will be listed under a folder that is added for that specific version of the Web Service. For example, three files will be listed under: C:\Program Files\Common Files\Microsoft shared\Web Server Extensions\12\ISAPI\ML\

·A DLL file, which gets deployed to the Global Assembly Cache (GAC).

After installation the Metalogix Extensions Web Service sits idle on the server until requests are made to it, by the Metalogix Content Matrix client. For more information about the Metalogix Extensions Web Service, please see the Installing the Metalogix Extensions Web Service page.

Using Older Versions of the Extensions Web Service


Can I use an older version of the Metalogix Extensions Web Service with a newer version of the Metalogix Content Matrix Console?


It is not recommended to use older versions of the Metalogix Extensions Web Service with newer build of Metalogix Content Matrix, but this is possible after build v5.0.0.6. In order to use an older version of the Web Service some configuration changes must be made. To do this, close the Metalogix Content Matrix Console and go to its installation folder (for example, [Drive]:\Program Files (x86)\Metalogix Content Matrix Console - SharePoint Edition). Find the WebServiceConfiguration.xml file, and edit it.

This file will list the default Web Service version number, which can be modified. The format of this entry should be:

<Server Name="default" WebServiceVersion="[Version Number5.0.0.6]" />

Once the old version number is specified, save the XML file and re-open the Metalogix Content Matrix Console.

It is possible to add additional lines to this code to specify server names. In most cases these additional lines only need to be added if connecting to different (or multiple) servers, and these other servers are using a different version of the Metalogix Extensions Web Service. Any number of lines can be added for additional servers. If added, any additional lines will apply the server name and version number to any Web Service connections that are made to the specified server. The default Web Service version number value will be used for all other connections. If connecting to a site that uses Alternate Access Mappings (AAM) that point to a different URL, a separate entry will need to be made for the AAM.

The format for any additional lines is:

<Server Name="http://[ServerName]" WebServiceVersion="" />

If a newer version of the Metalogix Content Matrix Console is installed the WebServiceConfiguration.xml file will be overwritten, so any manual changes that were made will need to be entered again.

Preserving IDs when Migrating a Custom List as a Folder


I am trying to migrate a SharePoint list from my source, and pasting it as a folder within an existing list on my target. The list is a "Custom List" template, and I am preserving item IDs. I am not seeing the results I was expecting, and it looks like content may have been overwritten or deleted. What could cause this issue?


If migrating a custom list as a folder, or migrating folders within a custom list, while using the Overwrite and Preserve IDs on items/folders in Lists options, any existing folders or items on the target that have the same ID as the folders/items migrating from the source will be deleted in order to preserve the IDs for this migrating content. This is expected behaviour.

For example, if you are more concerned with maintaining the items and folder structure, you can turn off the Preserve IDs on items/folders in Lists option, which will allow the folders and items to be properly added to the list, without overwriting any content.

Migrating JavaScript


Can I use Metalogix Content Matrix to migrate JavaScript content from my source to my target SharePoint server?


It is possible to migrate some JavaScript using Metalogix Content Matrix, depending on the type of JavaScript being migrated. If the JavaScript from the source is embedded in a Content Editor Web Part, or embedded in a publishing page (in a pages library), it should be migrated the same as other SharePoint content. If the JavaScript is not embedded in either of these, then it will not be migrated with Metalogix Content Matrix. JavaScript can only be migrated into SharePoint, in locations that SharePoint itself will allow JavaScript to be manually added (in web parts and publishing pages).

There are two things to keep in mind if migrating JavaScript that is embedded in web parts or publishing pages. The first is that any links in the JavaScript will not be corrected. This is because the links are also embedded in the content, so they would not be picked up as part of the link correction process. These links must be manually corrected. In order for Metalogix Content Matrix to correct these links it would have to edit the actual contents of the web part or publishing page, and this is something we try to avoid.

The second thing to keep in mind is that if the Reattach Publishing Page Layouts check-box is selected any customizations for the page (including JavaScript and any other customizations) will be lost.

Related Documents