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

Item Count Discrepancies


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?


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.

Keyboard Shortcuts


Are there any keyboard shortcuts in the Metalogix Content Matrix Console? If so, what are they?


Yes, there are a few basic keyboard shortcuts within the Metalogix Content Matrix Console. They are:

·Ctrl + A - This will Select All items within the Items view or in any of the logging sections (such as the Job List section or the Log Viewer).

·Ctrl + C - This will Copy any selected item(s) within Explorer view or Item view, including sites and lists. It will also copy any selected item(s) or information within the logging sections (such as the Job List section or the Log Viewer).

·Ctrl + V - This will Paste any selected item(s) within Explorer view or Item view, including sites and lists. It will also paste any selected item(s) or information within the logging sections (such as the Job List section or the Log Viewer).

·Delete - This will Delete any selected item(s). This applies to all views and items within Metalogix Content Matrix.

·Ctrl + P - This will open the Properties dialog for any selected item in Metalogix Content Matrix, in both the Explorer view and the Items view.

·Ctrl + S - This will open the Save dialog for the current Job list.

·F2 key - This will Rename any selected job list in the Job List in the main UI. Simply select the desired job list, in the Job List section, press F2, and type in the new name for the job list.

·F5 key - This will Refresh any selected node in the Explorer View. This is the same as using the Refresh node option in the context (right-click) menu.

License Key Troubleshooting


I have been unable to get Metalogix Content Matrix to recognize my license key. When I copy and paste it into the box, I get a "the specified license key is invalid" error.


Here are some things to check:

·Confirm that the license you are installing is for the correct application versions of Metalogix Content Matrix. Contact Quest to verify that it is.

·When performing an offline key activation, make sure to enter the long key in its entirety, including the "=" symbol at the end of it.

·Verify that you have write privileges to the registry. The installer will fail if the registry is locked. In some cases there may be a group policy that is preventing the user from adding the key in the registry, despite the user having the correct permissions.

·Some versions of Windows will automatically block write access to the registry under the user account, even if that account has write access to the registry. In this case you can go to the application installation folder, right click on the application executable, and choose 'Run as Administrator'. Then re-enter the license key.

Determining the Status of a Migration Running in the Background


Is there a way to determine what the status is for a migration that is running in the background?


Yes, this can be done. This is more of a workaround method that should achieve the same results.

For this method to work users must create a new batch file for the job list, and store it in a commonly accessible area on the file system. Give this job list the same name as the one that is, or will be, running in the background. After the main job is running in the background, the new job file can be opened in any users instance of Metalogix Content Matrix. When the new job is opened, users will be given a snapshot view of the job in progress (this is not a real-time update).

For example, let's say that a job file called "Big Job" is running in the background, and another user wants to determine the progress for this job. They would create a new Job file, and call it "Big Job" to match the existing (running) job and then place that file in a commonly accessible area on the file system. Next, they would open this new job file (the copy) in their instance of Metalogix Content Matrix. This should give the user a snapshot view of the original "Big Job" migration, in process, as it continues to run in the background.

Users can use this method to quickly determine how far along the migration is, and it's status.

Related Documents