Chat now with support
Chat with Support

Content Matrix 9.9 - SharePoint Edition

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
Team Site to Modern Team Site Migration SharePoint Sites to Modern Communication Site Migration Promotion of First Level Subsites to Site Collections MySite Migration "Share With" Metadata and "Sharing Links" Access Permissions Migration Records Center to SharePoint Online Migration Using the Import Pipeline Master Page Migration List Template Gallery Migration Content Types Migration Document Version and Checked Out File Limitations Ghosted and Un-Ghosted Page Migration Document Set Migration Navigation Migration Classic Web Parts Migration Site Theme Preservation Site Feature Migration Managed Metadata Migration Users and Permissions Migration BCS/BDC Data Migration OneNote Notebooks Migration Customized Form Pages Migration InfoPath Forms Migration SharePoint Workflow Migration Nintex Workflows and Forms Migration Link Correction StoragePoint Content Migration
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
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 Migration Frequently Asked Questions
DB_Owner Permission Keyboard Shortcuts Activating the License Key Silently License Key Troubleshooting Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Migrating SharePoint On Premises Using Proxies, Load Balancing or Alternate Access Mappings Extensions Web Service Installation Files Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint 2013 and Later Site Collection Creation Issue Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs When Migrating to SharePoint Online Retrying Failed Document Copies to SharePoint Online CSOM Connections Import Pipeline Batches Getting Stuck Migrating Content When the Source Custom List Template is Missing When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Error: 'The object is associated with property AssociatedMemberGroup.' Migration Error: 'ERROR, the batch will be resubmitted to the import pipeline' Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

Log Item Details

Navigation:  Saving or Running a Migration Job > Job Log Files >

Log Item Details

To view Log Item Details:

1.From the Log Viewer, select the item whose details you want to view.

2.Use one of the following options:

§Double-click on the item.


§Right-click and choose View Job Item.


§If the job is currently running, click Details>>.


The Job Details dialog contains the following information:

·Operation - The last operation performed on the item.

·Status – The status of the item. If a compare action is being performed then this could be: completed, different, or missing.

·Item Name - For items, the Item ID. For documents, the Filename.

·Time Started – The time the action for the item was started.

·Time Finished – The time the action for the item was finished.

·Bytes Copied – The  bytes (B) that were copied in the action. This will be displayed in KB in some cases.

·Source - The Source URL for the item.

·Target - Target URL for the item.

·Information - Provides an informational message about the item, such as. This section will provide a description for any different and/or missing attributes/metadata for an item.

·Details View - Any errors that were encountered with the item when an action was performed.  

·Content Comparer tab - Any differences between Source and Target content (from a compare action). You can display this information in either a Grid View, which displays a metadata property grid for the item, or as a Text View, which displays a XML text format of the item.  This option is most useful if Verbose Logging has been checked

You can also:

·Use [Search KBs] to have Content Matrix query the Quest Support Knowledge Base for relevant articles if you selected a failed item.

·Use [Copy] to copy all of the item information and details (including the Details tab) into the system’s clipboard.  You can then paste the information when it can then be pasted to another location. When pasted the information will look similar to that of the actual Log Item Details dialog. This can be used for easy copy/pasting of an items migration log details.

·Use [Prev] and [Next] buttons to move to the previous or next item on the list (if applicable).

Copying Job Logging to Other Applications

Navigation:  Saving or Running a Migration Job > Job Log Files >

Copying Job Logging to Other Applications

It is possible to copy the results of migration jobs from log files to other applications. This can be beneficial if you want to keep track of copy or incremental information outside of Content Matrix, or want to manipulate the information for reporting or retention purposes. The log information is copied as text, to the clipboard, and can then be pasted within any other application that allows text pasting. For example, if a copy action was made, the logging can be copied into a Word file, or into an Excel spreadsheet, then saved.

NOTE: Only the end results of the total action will be copied.

To copy the logging for a job list:

1.Select a job from the Job List.

2.Right-click, and choose Copy selected job to clipboard (alternately Ctrl+C can be used).

3.Open the desired target program (for example: Microsoft Word, Microsoft Excel, Notepad, etc), then paste the content into the application (Ctrl+V, or the paste command in the application itself).

NOTE:  The logging for each action within the list must be copied separately.

To copy the logging for job items:

·Select the desired job list or job item(s) that the logging is to be copied from, and open the job list to access the Log Viewer.

·Select any job items that are to be copied. Single or multiple items can be selected in the Log Viewer. In order to copy the logging for the entire job, all job items in the Log Viewer must be selected.

·When all of the desired items are selected, right-click on one of them, and select Copy Log Items to Clipboard, and select to either copy them with, or without details. The Details are a set of extra columns that are added to the logging. These columns are typically: Details, SourceContent, and TargetContent. These columns do not always contain extra information. The default copy option (Ctrl+C) is to copy the logging without the Details.

Coppy Log Item to Clipboard



Creating a Support Zip File for a Migration Job

Navigation:  Saving or Running a Migration Job > Job Log Files >

Creating a Support Zip File for a Migration Job

You can generate a zip file of data associated with a single migration job to help Quest Support facilitate troubleshooting.

The high-level data collected in the zip file includes:

·Application Settings files.

·Product information (product version, license, etc.).

·Information about the job (what action settings were set, the job log, etc.).

For a migration job to SharePoint Online that was run using the Import Pipeline, if there are batches with a Status of Failed or Warning an additional folder, <Date[YYYYMMDD]>_UploadManagerStatus, is automatically included for those batches only. This folder contains the same files as the API Support Zip file.

IMPORTANT:  Sensitive Information

Please review the contents of the zip file before sending it to Support.  While this feature attempts to only collect non-sensitive data, no guarantees can be made - it is up to you to ensure that any files in the zip folder are stripped of any confidential data. Regardless, Quest assures that the contents of the zip file will only be used for troubleshooting the associated support ticket.  For added security, Content Matrix removes the encrypted password and token information from the file.  

NOTE: Because passwords are removed, if you try to import a job from a Support zip file and there is no active connection to both the source and target, the import will fail. It is recommended that you create xml jobs using Export to Xml functionality instead of using the xml file generated by the Create Support Zip File operation. Refer to the Knowledge Base article While Importing a Job from a Support Zip File, the error “Could not load data: A password is required” is generated (4369247) ( for details.

To create a Support zip file:

1.In the Job List, select the job for which the zip file is to be generated.

2.Use one of the following options:

§In the main ribbon, click the Help tab, then Create Support Zip File.

§Right-click and choose Create Support Zip File.

3.Save the file to the desired location using the desired file name.

4.If you wish to review the zip file for sensitive information, click Yes to open the zip file. Once you are satisfied with the contents of the zip file, it can be sent to Quest Support to aid in troubleshooting.

Enabling Trace Logging

Navigation:  Saving or Running a Migration Job > Job Log Files >

Enabling Trace Logging

You can enable trace logging on the machine where Content Matrix is installed and migrations are run to assist Quest Support with troubleshooting.

NOTE:  For Distributed Migration, trace logging must be enabled on each agent machine.

To enable trace logging:

1.Open the file LogSettings.xml, which can be found in one of the following folders:

·If you are required to be a local administrator on the machine where Content Matrix is installed: C:\ProgramData\Metalogix


·If you are not required to be a local administrator on the machine where Content Matrix is installed: C:\Users\<username>\AppData\Roaming\Metalogix\Common

2.Set <LoggingLevel> to one of the values described in the following table.

WARNING:  When trace logging is enabled, entries are appended to the log file for each migration job that is run, and the same log file is used for all editions. This means the log file can become very large, which is why it is recommended that you only enable trace logging at the request of Quest Support.



None [Default]

Trace logging is disabled (i.e., no entries are written to the log file).


Only Error messages are logged.


Error and Debug messages are logged.

NOTE:  Debug should only be used for advanced troubleshooting as it may impact migration performance.

Log entries are written to the file MetalogixGlobalLog.txt, which is located in the same folder as LogSettings.xml.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating