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

Frequently Asked Questions

This section answers some of the most frequently asked questions about using Metalogix Content Matrix.

DB_Owner Permission

Question

Are read and write permissions to the SharePoint content database sufficient for the Metalogix Extensions Web Service to perform migration?

Answer

As you may know, the Metalogix Extensions Web Service requires read and write permissions to the Content Database, according to a Microsoft KB article (http://support.microsoft.com/kb/935751. However, this is only a solution if you have encountered the message "Unhandled Exception: system.IO.FileNotFoundException" when using the SharePoint object model. We have found that few users have reported this issue, since the Web Service account is usually granted the sysadmin server role, which has complete control over all database functions.

After some internal testing we have determined that the Web Service installing account requires more than read and write permissions to function without database errors.

1."db_owner" rights to the SharePoint Content Database is required.

If the Web Service account does not have the db_owner right to the SharePoint Content Database, Metalogix Content Matrix will not be able to migrate list items using the Web Service, and may receive one of the following errors:

4/19/2010 7:13:53 PM Error copying list item: 1/1 (id: 1, title: Get Started with Windows SharePoint Services!): Service Error: [MLSPService could not add items: MLSPServiceMethods.AddListItems() Failed: Cannot open database "WSS_Content" requested by the login. The login failed.

4/20/2010 10:21:01 AM Error copying list item: 1/2 (id: 1, title: Get Started with Windows SharePoint Services!): Service Error: [MLSPService could not add items: MLSPServiceMethods.AddListItems() Failed: Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))

2."db_owner" or "WSS_Content_Application_Pools" rights to the SharePoint Admin Content Database is required.

If the Web Service installing account does not have db_owner or WSS_Content_Application_Pools rights to the SharePoint_AdminContent, Metalogix Content Matrix will not be able to create/paste site collections, and will receive an error.

With these cases in mind we have determined that the Metalogix Extensions Web Service account should be granter the db_owner permission rights, at a minimum, to allow Metalogix Content Matrix to correctly migrate content to the target SharePoint instance.

Migrating with the Fabulous 40 Templates

Question

I am using the Fabulous 40 Templates that were released by Microsoft in my SharePoint Sites. Am I able to migrate the content that uses these templates with Metalogix Content Matrix Console?

Answer

Unfortunately Metalogix Content Matrix does not support the Fabulous 40 Templates that were released by Microsoft. These templates contain a number of customizations, and these customizations cause some problems for Metalogix Content Matrix when we try to migrate and map content. Metalogix Content Matrix is able to migrate some of the content, however, because of some of the customizations that have been made to the template, we can run into problems that prevent us from migrating other parts of the content correctly, or prevent us from migrating the pages at all.

While not able to migrate using the Fabulous 40 Templates, it is possible to create Site Collections using the .WSP-based templates, from the Fabulous 40, as long as these templates are deployed on the server beforehand. It is not possible for Metalogix Content Matrix to create any Site Collections using the .STP templates, since it is not possible to create Site Collections using these templates through the Web UI.

SharePoint 2010 does not support the Fabulous 40 Templates.

Item Count Discrepancies

Question

In the Explorer View tab the Item count for a list is different between my source and target. There seem to be more items on the source system (or more items on the target system). Why are the item count's different, and what could be causing this?

Answer

Metalogix Content Matrix gets its item count from SharePoint itself, and does not actually run its own count of the items.

The most common case where the number of items on the source is greater than the number of items on the target, is when migrating from SharePoint 2003 (SPS 2003 or WSS 2.0) to SharePoint 2007 or 2010. Lists in SharePoint 2003 use a different numbering logic then later versions of SharePoint, which is the likely cause of any count discrepancies. The numbering logic in SPS 2003 counts all the items in the list, but also counts folders and all of the item versions. Users can see a more accurate view of the number of items through the Items View tab, where they can see a breakdown of each item and the versions, by using the Show Version History button. The item count for a MOSS 2007 or SharePoint 2010 list will only count the number of actual items, and each version will be listed under its item (and not be counted). Folders will not be counted.

Let's look at an example where we have a SPS 2003 list that contains 50 items, where 40 of these items are versions. In this case Metalogix Content Matrix  will list the item count of the SPS 2003 list as 50 (counting both the actual items and the versions). After this list has been migrated to a MOSS 2007 (or SharePoint 2010) target, Metalogix Content Matrix will count the list as having only 10 items, because the 40 versions that exist will all be listed under each appropriate item. So it will count 10 items, which will all have version under them (if the specific item has versions), for a total of 40 item versions. On the target the combined total of the items and the versions will still be 50, but it is counted as 10, since versions are not counted as full items (more like extra metadata of an item).

If the SharePoint 2003 to SharePoint 2007 or 2010 is not the use case you are migrating with, there are a few things that can be checked to help determine what the differences might be, if any. A compare can be run between the source and target to help determine any differences. If the compare returns no reasonable results (any results that would account for the item count discrepancy), then it is recommended to manually look at the source and target to see if any items can be found that exist on one system but not the other. It is also a good idea to check the server that has more items, to make sure that nothing has been manually added since the migration.

In the case that there are more items on the target side as compared to the source, there is one other possibility. It is possible that there are some hidden lists/folders that are created on the target when a site is created. because they are hidden they would not be visible through the Metalogix Content Matrix Console or SharePoint UI, but they could still be included in the item count. It is also possible, though unlikely, that the value for the item count on one of the systems has been corrupted.

If no discrepancies can be found between the source and target difference in the item count, despite running a compare action or manually looking for differences, then it is generally safe to say that there are no real differences between the actual item count, and that the count itself is just displaying as different numbers.

Related Documents