I have exported my content to a CSV file, but when I open it in Microsoft Excel (or similar programs) the column value is incorrect, and the value covers multiple rows. What are the potential causes of this issue?
This issue is not actually caused by Metalogix Content Matrix Console. What is happening is that the value in one of the columns is actually exceeding the character length of the cell in Microsoft Excel.
In most cases, some of the page content is placed in a column and is then included in the CSV Export. Microsoft Excel has a maximum character limit of 32,767. If the exported column value is longer than the 32,767 character limit, the file will be incorrectly read, and Excel will run into issues when trying to open the CSV file. For more information on this character limit, refer to Microsoft Office documentation.
It is recommended that if users are exporting to CSV and think that one of the column values may exceed the 32,767 character limit, then that cell value should be broken down into multiple column values (the number of columns would depend on the column value's character length). The CSV file should then open correctly after being exported, and user should be able to work with the content before migration.
This section covers how to enable and use the debugging features of Metalogix Content Matrix Console. For more information on tests to perform, please contact Quest Support.
NOTE: This action only applies to Confluence, WordPress, Telligent and Other Blogs (XML-RPC) connections.
Enabling the Debug Feature
The steps for enabling the Debug feature will vary depending on the version of Metalogix Content Matrix being used.
Enabling the Debug Feature in v.5.0.1.01 and Later
1.On the system that the Metalogix Content Matrix Console is installed on, navigate to the AppData folder. An example of this location is:
<Drive>:\Users\<USER>\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - Blogs and Wikis Edition.
2.Once in this folder location, select the EnvironmentSettings.xml file, and open it for editing (right-click and choose Edit).
3.In the EnvironmentSettings.xml file, set the EnableDebug value to "True".
Note: In some cases the EnableDebug entry may not be visible within the EnvironmentSettings.xml file. In this case, users can copy and paste another entry in the file, starting with <XmlableEntry> and ending with </XmlableEntry>. In the copied entry, replace the key entry with "EnableDebug" and set the value to "True."
Below is an example of a completed entry:
<Key Type="System.String, mscorlib, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b77a5c561934e089">EnableDebug</Key>
<Value Type="System.String, mscorlib, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b77a5c561934e089">True</Value>
4.After the value has been set, save and close the EnvironmentSettings.xml file.
5.Restart the console. The Debug option should now appear in the context (right-click) menu for any selected source content.
Enabling the Debug Feature in Versions Earlier than 5.0.1.01
1.Create a desktop shortcut to the console. Do this by navigating to the application directory (e.g. C:\Program Files\Metalogix Software Corp\Metalogix Content Matrix Console - Blogs and Wikis Edition), right-clicking on the Application file, and select Send to > Desktop (create shortcut).
2.Right-click on the new desktop shortcut and select Properties.
3.Select the Target field and append -debug to the end as seen below (including the space between):
4.Click OK to close the Properties window.
After debug mode is enabled anytime the desktop shortcut is used the debug mode will open. To return the eRoom Edition to normal, users can either create a new shortcut, or remove the -debug from the target line in the shortcut properties.
Debugging a Connection
1.Launch the Metalogix Content Matrix Console using the modified shortcut (see above) and navigate to the source connection node that is experiencing issues using the Explorer View. Then right-click and select the Debug option.
Note: If you do not see the Run Diagnostics option, you may not have enabled the debug setup option correctly. Please see the Enabling the Debug Feature section above.
Does Metalogix Content Matrix Console - Blogs and Wikis Edition support migrating MediaWiki "Category" pages?
Yes, migrating "Category" pages for a MediaWiki connection is supported.
Pages in MediaWiki can have "Category" values applied to them. Each category that is created has it's own a root page that users can access to modify and add additional content into. These pages are visible in Metalogix Content Matrix Console - Blogs and Wikis Edition's Items View and will also be visible in the Explorer View if the Show Pages option is selected. These category root pages have two sections. The top section of the page is for user defined content, and the bottom portion of the page is a MediaWiki generated section that list all of the other pages that belong to that "Category".
When Metalogix Content Matrix migrates these category root pages as a site migration, the top section of the page (the user defined content) is added to the page body. At the same time the bottom section of the page (the MediaWiki generated list of links to other pages in the category) is appended to the target page content as a list of links. These links are only updated at the time of migration and will not be updated when any subsequent changes are made in the target environment.
How does Metalogix Content Matrix deal with environments that use proxies, load balancing and/or alternate access mappings (AAM)?
Metalogix Content Matrix Console should not run into any issues with these three things. Metalogix Content Matrix uses a Metalogix Extensions Web Service that deploys over a whole farm, and functions identically to a regular SharePoint web service. SharePoint web service's get the benefits of IIS redirection, proxy pushing, and anything else that SharePoint can utilize, such as Alternate Access Mappings (AAM). Since the Metalogix Extensions Web Service acts the same as a SharePoint web service it also gets all of these benefits.
Basically, if you can access the regular native web services with all of your network configurations active, then you should also be able to reach the Metalogix Extensions Web Service, and migrate your content.
In the case for load balanced environments the Metalogix Extensions Web Service would need to be deployed through the target side SharePoint farm. When the Web Service is installed it automatically gets deployed to all the SharePoint instances within that farm, as a SharePoint solution. Once the Web Service is installed on the target server, then load balancing should no longer be an issue.
There are, however, some cases where proxy settings may not work correctly by default. In these cases it is possible to set some specific proxy settings for the specified connection. Please see the Configuring Proxy Settings page for more details, or the Manually Configuring Proxy Settings page if the proxy settings need to be manually configured.