Are there any limitations when migrating versions and version metadata from a SharePoint 2003 (SPS 2003 or WSS 2.0) source?
Yes, there are some potential limitations when migrating versions and version data from a SharePoint 2003 (SPS 2003 or WSS 2.0) source. These potential limitations depend on what type of connection adapter is being used to the source SharePoint 2003 instance. There are only two possible connection types that can be made to SharePoint 2003 sources, the first is a Native Web Service (NWS) connection, and the second is a SharePoint Database (DB) connection. A breakdown of what version data is supported for each connection type is listed below.
Native Web Service (NWS) Connection
This connection type is the most limited for migrating SharePoint 2003 versions and version data. The NWS connection only supports the preservation of:
·The actual item or document that the versions exist on.
·The actual version numbers for each version that exists.
·The Authorship data for each version. The Authorship data consists of the Created, Created By, Modified, and Modified By metadata fields.
·The Comments field for each version will be preserved.
Any custom metadata that falls outside of these parameters (such as the Title field or any other custom fields) will not be fully preserved. While these columns/fields will still be migrated to the target, all of the values for these fields (for each version) will use the metadata from the most recent version data that exists in the migration.
SharePoint Database (DB) Connection
The SharePoint DB connection should be able to preserve all of the version information and metadata, including Authorship metadata and custom field metadata, that exists for each version that is being copied in the migration.
I have been trying to create a new Site Collection in SharePoint 2013/2016 through Metalogix Content Matrix but I have been encountering issues. Why is this happening? and what can I do about it?
Starting with SharePoint 2013, most web applications use claims authentication, but the Central Administration web application that manages the server level settings uses Classic authentication. When Metalogix Content Matrix Console connects to a SharePoint server it has to authenticate through a web application. When connected to a SharePoint 2013 or 2016 web application that uses Claims authentication, SharePoint itself can have trouble recognizing that the accessing User account has permissions in the web application areas that are managed by Classic authentication. This is also true if connected to a web application that uses Classic authentication, if trying to access an area managed by Claims authentication.
In SharePoint 2013 and 2016, the permissions to create Site Collections is managed by Classic authentication, so if connected through a Claims authentication web application users will receive a "401 Unauthorized" error message when trying to create a new Site Collection. This happens even if the user account has all of the appropriate permissions. If connecting through a Classic authentication web application, users will receive permission errors when trying to set any settings on a Site Collection that uses a Claims authentication web application, after the Site Collection is created.
From internal testing, we have determined that SharePoint 2013 connections that use the Local Object Model connection will not run into this issue. This is because the Local OM connection type does not run authentication through IIS, which appears to be a trigger point for the authentication issues.
From testing we have also determined that you are still able to create SharePoint 2013 Site Collections when using the Remote OM connection type, but in order to do this Metalogix Content Matrix Console must elevate your permissions for the creation step. Before elevating any credentials, Metalogix Content Matrix Console will run a preliminary check to ensure the migrating user has enough permissions initially to be able to use the elevated Site Collection creation. In order for these elevated permissions to be used, the migrating user account must explicitly (by name) have "Full Control" permissions on the Web Application that the Site Collection is being created on.
In the Remote OM connection case users can also create a Site Collection within any web application if they are a member of the Farm Administrator group in SharePoint and they are connected to Central Administration as a farm connection.
NOTE: All of the above is also true if you are migrating to a SharePoint 2010 environment that uses Claims authentication.
Possible Errors when Creating Site Collection in SharePoint 2013
Below is a list of errors (and their explanations) that you might encounter when trying to create Site Collections in SharePoint 2013 through Metalogix Content Matrix Console.
·Error Message 1 - Unable to create a site collection using Self Service Site Creation under the Administration Web Application.
Explanation/Resolution - The User is connected to the Central Administration web application (using a farm or web connection type) and is trying to create a Site Collection using Self Service mode. This is not allowed. You will need to use the Admin mode instead.
·Error Message 2 - Unable to obtain Web Application '<web application name>'.
Explanation/Resolution - Metalogix Content Matrix is unable to find the web application. This should not occur unless a serious issue within SharePoint has occured from the time the Site Collection configuration dialog was displayed, and the call to the Metalogix Extensions Web Service (for remote OM connections) was made to perform the Site Collection creation. Check your SharePoint environment, and resolve any issues. Then try again.
·Error Message 3 - Migrating user '<migrating user>' requires explicit Full Control on the web application where the site collection is intented to be created. If the migrating user is a member of the Farm Administrators group then connect to the Central Administration site and try again.
Explanation/Resolution - The migrating user has read permissions on the web application (using a farm or web connection type) that they're connected to, but does not have full control on the web application that they are trying to create the Site Collection in. To resolve this, the migrating user account must be added explicitly (by name) with Full Control to the respective Web Application that they are trying to create the site collection in. They can also create a Site Collection within any web application if they are a member of the Farm Administrator group in SharePoint, and they are connected to Central Administration as a farm connection.
I recently upgraded to Metalogix Content Matrix Console version v.6.2.x.x and my Job List database is failing to load. What might be causing this issue? and how can I fix it?
This issue was likely caused by a recent upgrade to Metalogix Content Matrix Console's security features. A security upgrade has been made in Metalogix Content Matrix Console version 126.96.36.199 and later. This change has resulted in two potential issues that users can encounter. These issues and their resolutions are:
·Issue 1: The Job List database failing to load.
Resolution: When the Metalogix Content Matrix Console client opens, an error message will prompt the user to open the Job List file again. Go down to the Job List section and click File > Open Job List. This will open a Browser window. Navigate to the location that contains the LST file for the Job List that was previously listed in the Job List section. Then select the LST file and click Open. The Job List will now be loaded and users can continue as normal.
Due to the security upgrades in version 188.8.131.52 and later, the security settings for the Job List need to be upgraded. Metalogix Content Matrix Console cannot do this while the job is actively selected, but can apply the update to the existing Job List the next time it is loaded back to the Job List section of the client application.
·Issue 2: Any connections that have had the Save my credentials check box selected will no longer have their passwords saved.
Resolution: For any connections that had their credentials previously saved by using the Save my credentials option, you will need to connect or reconnect to that environment and enter the password in again, then complete the connection. The security upgrade has caused the encryption file for any saved passwords within Metalogix Content Matrix Console to be upgraded, and to apply this upgrade to this file, any saved passwords must be re-entered.
Why is it that when I migrate a wiki page that has been modified using SharePoint Designer (SPD), web part zones and web parts are not preserved on the target?
To be able to migrate web part zones and web parts that were added using SPD:
·the SharePoint source version and the source connection type must support customized wiki page migration
·the Configuration Key AllowCustomizedWikiPageMigration in the ApplicationSettings.xml file must be set to True.
Supported Source SharePoint Versions and Connection Types
You can migrate custom web part zones and web parts added using SPD for the following SharePoint versions and connection types on the source.
Supported Source Version
Supported Source Connection Types
·Remote Object Model (MEWS)
·Local Object Model (OM)
·Remote Object Model (MEWS)
NOTE: Currently, customized wiki page migration is not supported for a SharePoint 2016 source.
Adding or Updating the Configuration Key AllowCustomizedWikiPageMigration
The Configuration Key AllowCustomizedWikiPageMigration was added to the ApplicationSettings.xml file in version 184.108.40.206, with a default value of True. (If you change the value to False, customized wiki page will be treated as normal wiki page and source content will not be preserved at target after migration.)
If you have upgraded from a version of Metalogix Content Matrix that is earler than 220.127.116.11, you can add this Configuration Key to the ApplicationSettings.xml file manually (ideally after the Configuration Key EnableSslForEmail).