I have been trying to create a new Site Collection in SharePoint 2013 or later 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 later 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 later, 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 or later 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 2013 or later 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 or later
Below is a list of errors (and their explanations) that you might encounter when trying to create Site Collections in SharePoint 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 occurred 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 or SharePoint 2019 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).
Is it possible to Preserve SharePoint list item IDs when migrating with a CSOM (Client Side Object Model) or Office 365 Tenant connection type on the target?
Yes, it is possible to preserve SharePoint list item IDs when migrating content to a target with a CSOM/Tenant connection.
Item IDs and Document IDs are a little different in SharePoint (not the SharePoint 2010 or 2013 Document ID feature), and this means that how they can be accessed through a CSOM connection is a little different. Preserving Document IDs will only work if an OM (Object Model) connection is made to the target, through either a Local OM or Remote OM (Extensions Web Service) connection. There are some limitations that can be encountered when trying to preserve Item IDs that are dependent on the connection type. There are three basic connection types that we need to keep in mind when looking at these limitations. They are:
·Local or Remote OM (Object Model) Connection - This connection type is made either when the Metalogix Content Matrix Console client application is installed directly on the target SharePoint server, or a remote connection is made using the Metalogix Extensions Web Service. This is valid for SharePoint 2007, 2010 and 2013. When this type of connection is made, Metalogix Content Matrix will be able to directly set the list item ID value in SharePoint through the Object Model. This value can be set as long as that specific value is not already being used by another list item.
·SharePoint CSOM (Client Side Object Model) or Office 365 Tenant Connection - This connection type is made when remotely connecting to an Office 365 environment. When connected to SharePoint Office 365 using a CSOM connection, Metalogix Content Matrix cannot directly set the list item ID value so another method must be used instead. The CSOM method for preserving the list item ID value is for Metalogix Content Matrix to create a temporary item and then deleting it. This creation and deletion process is done in batches and each item that is added will increment the ID value by 1. This will continue until the Metalogix Content Matrix reaches the necessary item ID value. If the target ID value is already in use, or if another item with a higher ID value exists in the list, then the item(s) will be added to the end of the target list (and not at its ID value). There are a few limitations to this method:
oOlder items that are placed into newer folders - The general case for this is if an older item, that has a lower ID number value is moved and placed into a folder that was more recently created (and has a higher ID number value). In this case, the items with the lower ID number values will be added after the folder is created, so their ID number values will not be preserved. For example, if a list item with an ID value of "12" is moved into a folder, and the folder has an ID value of "25". In this case the ID value for the item will not be preserved because the folder it is located in will not be created until ID 25 is created. So Metalogix Content Matrix will hold onto the item until the folder is created and then add it, but because the item ID has already been passed, its value cannot be preserved, and it will be given a new value by SharePoint after all other items have been added.
oLists containing default data - The general case for this scenario is when a SharePoint list (and not a Document Library) is created and SharePoint automatically adds a number of items (one or multiple) by default into that list. The default items that are created by SharePoint will also automatically be assigned an item ID value by SharePoint. When migrating this type of list their data will be deleted before the source content is migrated. The default added items will have ID values associated with them, and when the items are deleted those ID values will no longer be available, and Metalogix Content Matrix won't be able to track what the values were associated to. This can interfere with the ID value calculations that are made, and throw off the ID values that are being set during migration.
The most common place where users can see default list items created is when an "Announcements" list is created. Announcement list that are created by SharePoint will automatically create one item by default that is the "Welcome" message. However, when migrating with Metalogix Content Matrix and using the override option, users should not see this issue with Announcement lists because Metalogix Content Matrix will delete the list that is created by the site template, and create a new one. When the new list is created Metalogix Content Matrix is able to add the list items directly, and allows for the list item ID value to be set in the process. This is more likely to be an issue with SharePoint lists that have had their template modified to automatically generate a set of default items.
NOTE: When migrating SharePoint Task lists to a CSOM Office 365 connection, it is recommended that the Preserve IDs on items/folders in Lists option is selected. This is to help preserve the Related Items property for items in the Task list. If unchecked there is a small chance that the Related Items property may list incorrect files, because some of these files may be reffered to through the Item ID value.
·SharePoint NWS (Native Web Service) Connection - This connection type is used when remotely connecting to SharePoint 2007 or 2010. The NWS connection type does not have the ability to set or preserve the list item ID values.